netdev - Re: [Regression][BISECTED] kernel boot hang after 19898ce9cf8a ("wifi: iwlwifi: split 22000.c into multiple files")

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: <446c25888d9316d0f15e6bcc6ecb100dda99324e.camel@sipsolutions.net>
Date: Sun, 09 Jul 2023 20:07:40 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>, Linux regressions
	mailing list <regressions@...ts.linux.dev>
Cc: "Zhang, Rui" <rui.zhang@...el.com>, "Greenman, Gregory"
 <gregory.greenman@...el.com>, "linux-wireless@...r.kernel.org"
 <linux-wireless@...r.kernel.org>, "Baruch, Yaara" <yaara.baruch@...el.com>,
  "Ben Ami, Golan" <golan.ben.ami@...el.com>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>,  "Sisodiya, Mukesh"
 <mukesh.sisodiya@...el.com>, Kalle Valo <kvalo@...nel.org>, "David S.
 Miller" <davem@...emloft.net>,  Eric Dumazet <edumazet@...gle.com>, Paolo
 Abeni <pabeni@...hat.com>, netdev <netdev@...r.kernel.org>,  Jakub Kicinski
 <kuba@...nel.org>, Bagas Sanjaya <bagasdotme@...il.com>
Subject: Re: [Regression][BISECTED] kernel boot hang after 19898ce9cf8a
 ("wifi: iwlwifi: split 22000.c into multiple files")

On Sun, 2023-07-09 at 09:31 -0700, Linus Torvalds wrote:
> On Fri, 7 Jul 2023 at 03:55, Linux regression tracking (Thorsten
> Leemhuis) <regressions@...mhuis.info> wrote:
> > 
> > [CCing the regression list, netdev, the net maintainers, and Linus;
> > Johannes and Kalle as well, but just for the record, they afaik are
> > unavailable]
> 
> So I will release rc1 with this issue, but remind me - if it hasn't
> had any traction next week and the radio silence continues, I'll just
> revert it all.

Sorry. I got back home a few hours ago (for few days anyway) and I think
I already know what the issue is. I'll send a fix to try in a few
minutes, was just trying to collect all the reported-by etc.

There's clearly a separate bug in the init failure path, but the reason
it fails in the first place is a mismatch between different changes.

johannes