linux-kernel - Re: [syzbot] [wireless?] WARNING in rfkill

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: <13bd5c0903fef7d27b4af2a2e43e92a380f71968.camel@sipsolutions.net>
Date: Sat, 03 Jan 2026 14:05:18 +0100
From: Johannes Berg <johannes@...solutions.net>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+16210d09509730207241@...kaller.appspotmail.com>, 
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, 
	netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com, Krzysztof
 Kozlowski	 <krzk@...nel.org>
Subject: Re: [syzbot] [wireless?] WARNING in rfkill_unregister

On Fri, 2026-01-02 at 23:02 +0100, Aleksandr Nogikh wrote:
> 
> It depends on the particular case. It should be fairly easy to do for
> warnings (where there's just one clear stack trace) and potentially
> very tricky for task hungs (e.g.
> https://syzkaller.appspot.com/bug?extid=ef8f802abdb9a32343fc).

Makes sense. I see now that there was a recent attempt to fix this NFC
vs. rfkill deadlock issue (and this report is on a kernel before it), so
I guess let's leave it and see what happens :)

johannes