linux-kernel - Re: Linux 6.13-rc4

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20250113104030.GC5388@noisy.programming.kicks-ass.net>
Date: Mon, 13 Jan 2025 11:40:30 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Fabio Estevam <festevam@...x.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Waiman Long <longman@...hat.com>
Subject: Re: Linux 6.13-rc4

On Sat, Jan 11, 2025 at 02:39:57PM -0800, Guenter Roeck wrote:

> The patch is queued in -next, but not in pending-fixes, so I assume that
> "people just decided it wasn't critical enough" is accurate.

I had a look to see where the patch had gone and indeed, it sits in
tip/locking/core, which is the -next branch.

Notably it lacks a Fixes tag, which is typically required for /urgent
stuff.

If Linus wants it now, I suppose I can send him a pull for it, but
otherwise, it'll got in during the merge window, which is soon upon us
anyway.