public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/30270] New: syslog: openlog with NDELAY, but seccomp still requires openat(2) and lseek(2)?
@ 2023-03-23 23:27 steffen at sdaoden dot eu
  2023-03-24 11:47 ` [Bug libc/30270] " schwab@linux-m68k.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: steffen at sdaoden dot eu @ 2023-03-23 23:27 UTC (permalink / raw)
  To: glibc-bugs

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-04-03 23:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-23 23:27 [Bug libc/30270] New: syslog: openlog with NDELAY, but seccomp still requires openat(2) and lseek(2)? 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
2023-04-03 22:26 ` steffen at sdaoden dot eu
2023-04-03 23:37 ` adhemerval.zanella at linaro dot org

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).