linux-kernel - RE: [PATCH] Revert "wifi: iwlwifi: trans: remove STATUS

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: <DM3PPF63A6024A91EFB76D52F9590E82C30A390A@DM3PPF63A6024A9.namprd11.prod.outlook.com>
Date: Tue, 27 Jan 2026 13:22:06 +0000
From: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@...el.com>
To: Chris Bainbridge <chris.bainbridge@...il.com>
CC: "kvalo@...nel.org" <kvalo@...nel.org>, "Berg, Johannes"
	<johannes.berg@...el.com>, "benjamin@...solutions.net"
	<benjamin@...solutions.net>, "gustavoars@...nel.org" <gustavoars@...nel.org>,
	"linux-intel-wifi@...el.com" <linux-intel-wifi@...el.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH] Revert "wifi: iwlwifi: trans: remove STATUS_SUSPENDED"



> -----Original Message-----
> From: Chris Bainbridge <chris.bainbridge@...il.com>
> Sent: Tuesday, January 27, 2026 2:22 PM
> To: Korenblit, Miriam Rachel <miriam.rachel.korenblit@...el.com>
> Cc: kvalo@...nel.org; Berg, Johannes <johannes.berg@...el.com>;
> benjamin@...solutions.net; gustavoars@...nel.org; linux-intel-wifi@...el.com;
> linux-wireless@...r.kernel.org; netdev@...r.kernel.org; linux-
> kernel@...r.kernel.org; stable@...r.kernel.org
> Subject: Re: [PATCH] Revert "wifi: iwlwifi: trans: remove STATUS_SUSPENDED"
> 
> On Tue, Jan 27, 2026 at 05:05:31AM +0000, Korenblit, Miriam Rachel wrote:
> >
> > Just making sure: have you been able to reproduce the assert
> (ADVANCED_SYSASSERT in the log), and then the panic didn't happen?
> 
> Yes, the ADVANCED_SYSASSERT was logged but there was no subsequent null
> pointer dereference.
> 
> > If yes, please test the attached patch, which is supposed to fix the assert itself.
> With this, you are not even supposed to see an assert.
> 
> I ran this through 15 suspend/resume cycles with network traffic. The
> ADVANCED_SYSASSERT did not occur, so it looks like the patch does fix the
> SYSASSERT. There was a warning logged once out of the 15 cycles:
> 
> I think that this is probably a different bug though - checking previous logs with
> journalctl, I see the same warning occurred once with 6.17.0-06871-
> gf79e772258df which predates the "remove STATUS_SUSPENDED"
> commit.

Thanks for the help!

Regarding the warning, please open Bugzilla ticket for that

Miri