linux-kernel - Re: [PATCH v4 0/3] Fix bugs and performance of kstack offset randomisation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f17631fb-a773-4be9-9329-96026f962f3f@intel.com>
Date: Mon, 19 Jan 2026 08:51:15 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Kees Cook <kees@...nel.org>, Ryan Roberts <ryan.roberts@....com>,
 Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>,
 Huacai Chen <chenhuacai@...nel.org>,
 Madhavan Srinivasan <maddy@...ux.ibm.com>,
 Michael Ellerman <mpe@...erman.id.au>, Paul Walmsley <pjw@...nel.org>,
 Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
 Heiko Carstens <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>,
 Alexander Gordeev <agordeev@...ux.ibm.com>,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
 "Gustavo A. R. Silva" <gustavoars@...nel.org>, Arnd Bergmann
 <arnd@...db.de>, Mark Rutland <mark.rutland@....com>,
 "Jason A. Donenfeld" <Jason@...c4.com>, Ard Biesheuvel <ardb@...nel.org>,
 Jeremy Linton <jeremy.linton@....com>,
 David Laight <david.laight.linux@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 loongarch@...ts.linux.dev, linuxppc-dev@...ts.ozlabs.org,
 linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org,
 linux-hardening@...r.kernel.org
Subject: Re: [PATCH v4 0/3] Fix bugs and performance of kstack offset
 randomisation

On 1/19/26 08:44, Kees Cook wrote:
>> Like you noted, this is surprising. This would be a good thing to
>> make sure it goes in very early after -rc1 and gets plenty of wide
>> testing.
> Right, we are pretty late in the dev cycle (rc6). It would be
> prudent to get this into -next after the coming rc1 (1 month from
> now).
> 
> On the other hand, the changes are pretty "binary" in the sense that
> mistakes should be VERY visible right away. Would it be better to
> take this into -next immediately instead?
I think it can go into -next ASAP. It's just a matter of when it goes to
Linus.