[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240507.aevi0xaeWohb@digikod.net>
Date: Tue, 7 May 2024 17:42:34 +0200
From: Mickaël Salaün <mic@...ikod.net>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Kees Cook <keescook@...omium.org>,
Christian Brauner <brauner@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jakub Kicinski <kuba@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>,
Mark Brown <broonie@...nel.org>, Sasha Levin <sashal@...nel.org>,
Shengyu Li <shengyu.li.evgeny@...il.com>, Shuah Khan <shuah@...nel.org>,
Shuah Khan <skhan@...uxfoundation.org>, Bagas Sanjaya <bagasdotme@...il.com>,
Brendan Higgins <brendanhiggins@...gle.com>, David Gow <davidgow@...gle.com>,
"David S . Miller" <davem@...emloft.net>, Florian Fainelli <florian.fainelli@...adcom.com>,
Günther Noack <gnoack@...gle.com>, Jon Hunter <jonathanh@...dia.com>, Ron Economos <re@...z.net>,
Ronald Warsow <rwarsow@....de>, Stephen Rothwell <sfr@...b.auug.org.au>,
Will Drewry <wad@...omium.org>, kernel test robot <oliver.sang@...el.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, netdev@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v6 00/10] Fix Kselftest's vfork() side effects
On Tue, May 07, 2024 at 07:12:51AM GMT, Sean Christopherson wrote:
> On Mon, May 06, 2024, Kees Cook wrote:
> > On Mon, May 06, 2024 at 06:55:08PM +0200, Mickaël Salaün wrote:
> > > Shuah, I think this should be in -next really soon to make sure
> > > everything works fine for the v6.9 release, which is not currently the
> > > case. I cannot test against all kselftests though. I would prefer to
> > > let you handle this, but I guess you're not able to do so and I'll push
> > > it on my branch without reply from you. Even if I push it on my branch,
> > > please push it on yours too as soon as you see this and I'll remove it
> > > from mine.
> >
> > Yes, please. Getting this into v6.9 is preferred,
>
> Very strongly prefered for KVM selftests. The negative impact on KVM isn't that
> the bugs cause failures, it's that they cause false passes, which is far worse
> (and why the bugs went unnoticed for most of the cycle).
FYI it's now in linux-next.
Powered by blists - more mailing lists