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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAHk-=wiBZgXXE8mnjRxs_coxvwLTneC_LpiYntfyFPzvTkBg5g@mail.gmail.com>
Date: Sat, 11 Jan 2025 11:54:13 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: 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>, 
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: Linux 6.13-rc4

Coming back to this, because I'll obviously do rc7 tomorrow, and I'd
like any known silly issues to be sorted out.

On Mon, 23 Dec 2024 at 04:16, Guenter Roeck <linux@...ck-us.net> wrote:
>
> ARM: imx: Re-introduce the PINCTRL selection
> locking/lockdep: Enforce PROVE_RAW_LOCK_NESTING only if ARCH_SUPPORTS_RT

The pinctrl one has made it to me, but the PROVE_RAW_LOCK_NESTING one
(that apparently causes "BUG: Invalid wait context" issues on odd
architectures with specific configs) has not.

Maybe the issue got sorted out some other way, and I just haven't
tracked things properly?

Or maybe this just got dropped on the floor in the haze that was the
Xmas break? I see that Peter committed it:

  https://lore.kernel.org/all/173313861411.412.6467281091993873078.tip-bot2@tip-bot2/

It's also possible that people just decided it wasn't critical enough,
and it's pending for later?

              Linus