all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 56359@debbugs.gnu.org
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Sat, 16 Jul 2022 12:50:01 +0200	[thread overview]
Message-ID: <2094647B-7360-41F4-8AB0-ADFC835288E8@gmail.com> (raw)
In-Reply-To: <b4r12mj6fu.fsf@fencepost.gnu.org>



> Am 16.07.2022 um 01:35 schrieb Glenn Morris <rgm@gnu.org>:
> 
> Philipp Stephani wrote:
> 
>> Does the attached patch fix the issue?
> 
> Not entirely. I have to also allow "clone3", then it passes.

Hmm, I'm not sure we should allow clone3 unconditionally since it can do lots of things, and I'd expect that its capabilities will only grow over time. OTOH, BPF (or at least the libseccomp library) don't support pointer indirections which would be needed to inspect the structure fields. See https://lwn.net/Articles/822256/.
Any opinions?




  reply	other threads:[~2022-07-16 10:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 17:45 bug#56359: seccomp test failures on RHEL 9.0 Glenn Morris
2022-07-15 14:12 ` Philipp Stephani
2022-07-15 23:35   ` Glenn Morris
2022-07-16 10:50     ` Philipp Stephani [this message]
2022-08-20 12:37       ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11  0:54         ` Lars Ingebrigtsen
2022-10-11 12:36           ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11 17:43             ` Paul Eggert
2022-10-11 19:47               ` Lars Ingebrigtsen
2022-10-18  9:32                 ` Philipp Stephani
2022-10-06 16:56 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 11:56   ` Lars Ingebrigtsen

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=2094647B-7360-41F4-8AB0-ADFC835288E8@gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=56359@debbugs.gnu.org \
    --cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.