From: Johannes Berg <johannes@sipsolutions.net>
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+16210d09509730207241@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [syzbot] [wireless?] WARNING in rfkill_unregister
Date: Sat, 03 Jan 2026 14:05:18 +0100 [thread overview]
Message-ID: <13bd5c0903fef7d27b4af2a2e43e92a380f71968.camel@sipsolutions.net> (raw)
In-Reply-To: <CANp29Y6NNtie6ZTsFbYUfhubEYW2A-K44B0-TZC=b3+OZcz-Rg@mail.gmail.com> (sfid-20260102_230310_438801_8E58F90B)
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
prev parent reply other threads:[~2026-01-03 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 1:20 [syzbot] [wireless?] WARNING in rfkill_unregister syzbot
2026-01-01 12:07 ` Johannes Berg
2026-01-02 10:00 ` Krzysztof Kozlowski
2026-01-02 10:28 ` Tetsuo Handa
2026-01-02 10:32 ` Johannes Berg
2026-01-02 22:02 ` Aleksandr Nogikh
2026-01-03 13:05 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13bd5c0903fef7d27b4af2a2e43e92a380f71968.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzbot+16210d09509730207241@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox