From: Ping-Ke Shih <pkshih@realtek.com>
To: syzbot <syzbot+392a2c3f461094707435@syzkaller.appspotmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>
Subject: RE: [syzbot] [wireless?] WARNING in __alloc_workqueue
Date: Fri, 12 Dec 2025 00:21:14 +0000 [thread overview]
Message-ID: <a18557c761d047d7bc4950c3c18d4b85@realtek.com> (raw)
In-Reply-To: <693aca04.050a0220.4004e.0346.GAE@google.com>
> WARNING: kernel/workqueue.c:5701 at __alloc_workqueue+0x114c/0x1810 kernel/workqueue.c:5701, CPU#0:
This problem was addressed by Bitterblue Smith [1].
[1] https://patchwork.kernel.org/project/linux-wireless/patch/d57efe48-b8ff-4bf1-942c-7e808535eda6@gmail.com/
prev parent reply other threads:[~2025-12-12 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 13:41 [syzbot] [wireless?] WARNING in __alloc_workqueue syzbot
2025-12-12 0:21 ` Ping-Ke Shih [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=a18557c761d047d7bc4950c3c18d4b85@realtek.com \
--to=pkshih@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+392a2c3f461094707435@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.