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: Mon, 03 Apr 2023 22:26:28 +0000	[thread overview]
Message-ID: <bug-30270-131-SKczEO34Qb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30270-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30270

Steffen Nurpmeso <steffen at sdaoden dot eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Steffen Nurpmeso <steffen at sdaoden dot eu> ---
Well i mean OpenBSD, yes.  But since that shall also go FreeBSD i had to
outsource logging to a dedicated (fork(2)ed) process, before entering
seccomp(2).  I think this is the only viable way to do this, then.
(Having a text file with something like "malloc - mmap munmap mprotect" would
be cool nonetheless, so one could use grep(1) and such to build a list of
syscalls for at least some C library use cases.  Ok: where to stop.  I do not
know.)
Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-04-03 22:26 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
2023-04-03 22:26 ` steffen at sdaoden dot eu [this message]
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-SKczEO34Qb@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: link
Be 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).