From: Paul Eggert <eggert@cs.ucla.edu>
To: "Basil L. Contovounesios" <contovob@tcd.ie>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>,
Philipp Stephani <p.stephani2@gmail.com>,
56359@debbugs.gnu.org
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Tue, 11 Oct 2022 10:43:45 -0700 [thread overview]
Message-ID: <dccacd28-1b58-8653-0444-1bc2e0ca3a23@cs.ucla.edu> (raw)
In-Reply-To: <87lepm5yfo.fsf@tcd.ie>
On 2022-10-11 05:36, Basil L. Contovounesios wrote:
> Lars Ingebrigtsen [2022-10-11 02:54 +0200] wrote:
>
>> I've now applied Philipp's patch (adding gettid), and Paul has fixed
>> other bits here in 345de32a.
I didn't know about Bug#56359 when I "fixed" those other bits.
My "fix" involved allowing all uses of clone3, which (as Philipp noted
in August) is problematic. I'm not sure what's being tested for, but if
clone3 lets you evade the checks then the test is arguably more trouble
than it's worth. Would marking it as :unstable lessen the number of
false alarms we're getting? If not, perhaps we should remove it or mark
it as :dont-use-unless-you-know-what-youre-doing or whatever.
next prev parent reply other threads:[~2022-10-11 17:43 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dccacd28-1b58-8653-0444-1bc2e0ca3a23@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=56359@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=p.stephani2@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).