public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steffen at sdaoden dot eu" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30270] syslog: openlog with NDELAY, but seccomp still requires openat(2) and lseek(2)? Date: Fri, 24 Mar 2023 19:22:34 +0000 [thread overview] Message-ID: <bug-30270-131-guux01rrbB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30270-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30270 --- Comment #3 from Steffen Nurpmeso <steffen at sdaoden dot eu> --- I am explicitly doing "%.950s" to avoid taking the alloc path. 'Would have hoped NDELAY gets over some.. i do have /* syslog (plus reopen) */\ a_SEND,\ a_ALLOW(SYS_openat),\ a_ALLOW(SYS_lseek),\ a_ALLOW(SYS_socket),\ a_ALLOW(SYS_connect),\ a_ALLOW(SYS_getpid),\ unfortunately (i use LOG_PID). (I am currently wondering whether i can really do enable seccomp(2) for this by default, sitting on a moving black box.) Patch 4 is (CRUX Linux, core collection) Commit: Juergen Daubert <jue@jue.li> CommitDate: 2023-02-27 12:54:14 +0100 glibc: sync with upstream 2.36 branch --- glibc/.signature | 7 +- glibc/Pkgfile | 8 +- glibc/glibc-2.35-make-4.4-MAKEFLAGS.patch | 102 ---------- glibc/{glibc-2.36-3.patch => glibc-2.36-4.patch} | 1430 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- 4 files changed, 1428 insertions(+), 119 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-24 19:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-23 23:27 [Bug libc/30270] New: " steffen at sdaoden dot eu 2023-03-24 11:47 ` [Bug libc/30270] " schwab@linux-m68k.org 2023-03-24 11:50 ` adhemerval.zanella at linaro dot org 2023-03-24 19:22 ` steffen at sdaoden dot eu [this message] 2023-04-03 22:26 ` steffen at sdaoden dot eu 2023-04-03 23:37 ` adhemerval.zanella at linaro dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30270-131-guux01rrbB@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).