[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202403050141.C8B1317C9@keescook>
Date: Tue, 5 Mar 2024 01:43:14 -0800
From: Kees Cook <keescook@...omium.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Mark Brown <broonie@...nel.org>, davem@...emloft.net,
netdev@...r.kernel.org, edumazet@...gle.com, pabeni@...hat.com,
shuah@...nel.org, linux-kselftest@...r.kernel.org, mic@...ikod.net,
linux-security-module@...r.kernel.org, jakub@...udflare.com
Subject: Re: [PATCH v4 00/12] selftests: kselftest_harness: support using
xfail
On Mon, Mar 04, 2024 at 03:39:02PM -0800, Jakub Kicinski wrote:
> On Mon, 4 Mar 2024 15:14:04 -0800 Kees Cook wrote:
> > > Ugh, I'm guessing vfork() "eats" the signal, IOW grandchild signals,
> > > child exits? vfork() and signals.. I'd rather leave to Kees || Mickael.
> >
> > Oh no, that does seem bad. Since Mickaƫl is also seeing weird issues,
> > can we drop the vfork changes for now?
>
> Seems doable, but won't be a simple revert. "drop" means we'd need
> to bring ->step back. More or less go back to v3.
I think we have to -- other CIs are now showing the most of seccomp
failing now. (And I can confirm this now -- I had only tested seccomp
on earlier versions of the series.)
--
Kees Cook
Powered by blists - more mailing lists