GNU bug report logs - #56359
seccomp test failures on RHEL 9.0

Previous Next

Full log

View this message in rfc822 format

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: "Basil L. Contovounesios" <contovob <at> tcd.ie>, Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Glenn Morris <rgm <at> gnu.org>, Philipp Stephani <p.stephani2 <at> gmail.com>, 56359 <at> debbugs.gnu.org
Subject: bug#56359: seccomp test failures on RHEL 9.0
Date: Tue, 11 Oct 2022 10:43:45 -0700

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.