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] New: syslog: openlog with NDELAY, but seccomp still requires openat(2) and lseek(2)? Date: Thu, 23 Mar 2023 23:27:46 +0000 [thread overview] Message-ID: <bug-30270-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30270 Bug ID: 30270 Summary: syslog: openlog with NDELAY, but seccomp still requires openat(2) and lseek(2)? Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: steffen at sdaoden dot eu CC: drepper.fsp at gmail dot com Target Milestone: --- Just an observation (2.36 patch 4), but in order to be able to use syslog in a seccomp protected program i had to add the two mentioned to the list of allowed system calls, even though openlog(3) was called with NDELAY. Just an observation, but would be cool to be fixed i thought. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-03-23 23:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-23 23:27 steffen at sdaoden dot eu [this message] 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 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@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).