From: syzbot <syzbot+c92af8613ad38696ff09@syzkaller.appspotmail.com>
To: jchuang26@m.fudan.edu.cn, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] INFO: task hung in ieee80211_register_hw (8)
Date: Tue, 15 Sep 2026 04:26:03 -0700 [thread overview]
Message-ID: <6aa92b4b.4c28b7d0.c1bba.0039.GAE@google.com> (raw)
In-Reply-To: <6aa8de92.bf2fa351.a84d0.48e1SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: task hung in netdev_work_proc
INFO: task kworker/1:1:30 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:1 state:D stack:25352 pid:30 tgid:30 ppid:2 task_flags:0x4208060 flags:0x00080000
Workqueue: events netdev_work_proc
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5520 [inline]
__schedule+0x17db/0x58f0 kernel/sched/core.c:7270
__schedule_loop kernel/sched/core.c:7347 [inline]
schedule+0x164/0x2b0 kernel/sched/core.c:7362
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7419
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0x7c1/0x1550 kernel/locking/mutex.c:821
netdev_work_proc+0x6f/0x770 net/core/netdev_work.c:132
process_one_work kernel/workqueue.c:3396 [inline]
process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
kthread+0x38b/0x480 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
INFO: task syz-executor:6137 blocked for more than 152 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22248 pid:6137 tgid:6137 ppid:6131 task_flags:0x400140 flags:0x00080000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5520 [inline]
__schedule+0x17db/0x58f0 kernel/sched/core.c:7270
__schedule_loop kernel/sched/core.c:7347 [inline]
schedule+0x164/0x2b0 kernel/sched/core.c:7362
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7419
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0x7c1/0x1550 kernel/locking/mutex.c:821
Tested on:
commit: 6f157f39 Merge branch 'remove-comma-after-sentinel-ent..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=178d5925580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba53f227359c9d59
dashboard link: https://syzkaller.appspot.com/bug?extid=c92af8613ad38696ff09
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=100148c9580000
next parent reply other threads:[~2026-09-15 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6aa8de92.bf2fa351.a84d0.48e1SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-15 11:26 ` syzbot [this message]
[not found] <6aa8a19a.a9d33702.1eae08.2bc2SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-15 9:34 ` syzbot
[not found] <6aa7d932.ab0bb76a.688f5.afb7SMTPIN_ADDED_BROKEN@gmr-mx.google.com>
2026-09-14 15:44 ` syzbot
2026-09-12 9:57 syzbot
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=6aa92b4b.4c28b7d0.c1bba.0039.GAE@google.com \
--to=syzbot+c92af8613ad38696ff09@syzkaller.appspotmail.com \
--cc=jchuang26@m.fudan.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®