[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <05F133C4-DB2D-4186-9243-E9E18FCBF745@kernel.org>
Date: Tue, 26 Nov 2024 15:09:55 +1000
From: Kees Cook <kees@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: linux-kernel@...r.kernel.org, Alexander Viro <viro@...iv.linux.org.uk>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
"Eric W. Biederman" <ebiederm@...ssion.com>, Nir Lichtman <nir@...htman.org>,
Tycho Andersen <tandersen@...flix.com>,
Vegard Nossum <vegard.nossum@...cle.com>
Subject: Re: [GIT PULL] execve updates for v6.13-rc1 (take 2)
On November 26, 2024 9:40:22 AM GMT+10:00, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>On Thu, 21 Nov 2024 at 06:53, Kees Cook <kees@...nel.org> wrote:
>>
>> Please pull these execve updates for v6.13-rc1 (take 2). I've dropped
>> the argv[0] vs "comm" setting patches. We'll work on the better solution
>> for the next merge window.
>
>Yeah, I was pulling this, and then noted that the selftest is now
>documented to be that garbage.
>
>So I unpulled again.
Okay. I'd left it because I figured we'd be tweaking it for the new implementation, but yeah I can just rework it all then.
For the new implementation, do you want to wait a full dev cycle for it to bake in -next or should I send what I proposed based on your and Al's suggestions for this merge window?
-Kees
--
Kees Cook
--
Kees Cook
Powered by blists - more mailing lists