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] [day] [month] [year] [list]

Message-ID: <dd60a592-f680-47fb-8d3a-a4567e3393cc@roeck-us.net>
Date: Sat, 11 Jan 2025 14:39:57 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
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

On 1/11/25 11:54, Linus Torvalds wrote:
> 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?
> 

The problem is still seen as of v6.13-rc6-130-g2144da2.

[    1.009913] =============================
[    1.010206] [ BUG: Invalid wait context ]
[    1.010587] 6.13.0-rc6+ #1 Not tainted
[    1.010950] -----------------------------
[    1.011253] swapper/0/1 is trying to lock:
[    1.011579] 0000000001b81558 (pci_poke_lock){....}-{3:3}, at: pci_config_read16+0x8/0x80
[    1.012345] other info that might help us debug this:
[    1.012668] context-{5:5}
[    1.012968] 2 locks held by swapper/0/1:
[    1.013273]  #0: fffff800042b50f8 (&dev->mutex){....}-{4:4}, at: __driver_attach+0x80/0x160
[    1.013672]  #1: 0000000001d41930 (pci_lock){....}-{2:2}, at: pci_bus_read_config_word+0x18/0x80
[    1.014060] stack backtrace:
[    1.014426] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.13.0-rc6+ #1
[    1.014880] Call Trace:
[    1.015215] [<0000000000500590>] __lock_acquire+0xa50/0x3160
[    1.015553] [<00000000005037a8>] lock_acquire+0xe8/0x340
[    1.015857] [<0000000001101ffc>] _raw_spin_lock_irqsave+0x3c/0x80
[    1.016165] [<00000000004600c8>] pci_config_read16+0x8/0x80
[    1.016466] [<0000000000460ccc>] sun4u_read_pci_cfg+0x12c/0x1a0
[    1.016770] [<0000000000b9f69c>] pci_bus_read_config_word+0x3c/0x80
[    1.017078] [<0000000000ba8b98>] pci_find_capability+0x18/0xa0
[    1.017382] [<0000000000ba2690>] set_pcie_port_type+0x10/0x160
[    1.017683] [<000000000045f338>] pci_of_scan_bus+0x158/0xb00
[    1.017984] [<0000000000428c98>] pci_scan_one_pbm+0xd0/0xf8
[    1.018284] [<0000000000462a14>] sabre_probe+0x1f4/0x5c0
[    1.018585] [<0000000000c3d4a8>] platform_probe+0x28/0x80
[    1.018882] [<0000000000c3abb8>] really_probe+0xb8/0x340
[    1.019180] [<0000000000c3afe4>] driver_probe_device+0x24/0xe0
[    1.019487] [<0000000000c3b20c>] __driver_attach+0x8c/0x160
[    1.019793] [<0000000000c389b4>] bus_for_each_dev+0x54/0xc0

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.

Guenter