From: syzbot <syzbot+f2fbf7478a35a94c8b7c@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, andrew+netdev@lunn.ch, andrew@lunn.ch,
andrii@kernel.org, ast@kernel.org, bp@alien8.de,
dave.hansen@linux.intel.com, davem@davemloft.net,
edumazet@google.com, hpa@zytor.com, jason@zx2c4.com,
kuba@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, pabeni@redhat.com, sdf@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
wireguard@lists.zx2c4.com, x86@kernel.org
Subject: Re: [syzbot] [wireguard?] INFO: task hung in wg_netns_pre_exit (5)
Date: Sun, 08 Mar 2026 07:56:21 -0700 [thread overview]
Message-ID: <69ad8e15.050a0220.310d8.000d.GAE@google.com> (raw)
In-Reply-To: <66f49736.050a0220.211276.0036.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: c113d5e32678 Merge branch 'net-spacemit-a-few-error-handli..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=13a4875a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=779072223d02a312
dashboard link: https://syzkaller.appspot.com/bug?extid=f2fbf7478a35a94c8b7c
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10cf3fe6580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b5c8ba580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1a0aa684791/disk-c113d5e3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d0461aed5ba/vmlinux-c113d5e3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/05b26502bb1f/bzImage-c113d5e3.xz
The issue was bisected to:
commit d4dfc5700e867b22ab94f960f9a9972696a637d5
Author: Andrii Nakryiko <andrii@kernel.org>
Date: Tue Mar 19 23:38:49 2024 +0000
bpf: pass whole link instead of prog when triggering raw tracepoint
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ccbc58580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=142cbc58580000
console output: https://syzkaller.appspot.com/x/log.txt?x=102cbc58580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f2fbf7478a35a94c8b7c@syzkaller.appspotmail.com
Fixes: d4dfc5700e86 ("bpf: pass whole link instead of prog when triggering raw tracepoint")
INFO: task kworker/u8:7:1016 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u8:7 state:D stack:25664 pid:1016 tgid:1016 ppid:2 task_flags:0x4208060 flags:0x00080000
Workqueue: netns cleanup_net
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5295 [inline]
__schedule+0x15dd/0x52d0 kernel/sched/core.c:6908
__schedule_loop kernel/sched/core.c:6990 [inline]
schedule+0x164/0x360 kernel/sched/core.c:7005
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7062
__mutex_lock_common kernel/locking/mutex.c:692 [inline]
__mutex_lock+0x7fe/0x1300 kernel/locking/mutex.c:776
wg_netns_pre_exit+0x1c/0x200 drivers/net/wireguard/device.c:419
ops_pre_exit_list net/core/net_namespace.c:161 [inline]
ops_undo_list+0x187/0x940 net/core/net_namespace.c:234
cleanup_net+0x56b/0x800 net/core/net_namespace.c:704
process_one_work kernel/workqueue.c:3275 [inline]
process_scheduled_works+0xb02/0x1830 kernel/workqueue.c:3358
worker_thread+0xa50/0xfc0 kernel/workqueue.c:3439
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2026-03-08 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 23:05 syzbot
2025-10-20 1:52 ` syzbot
2025-10-20 19:23 ` syzbot
2026-03-08 14:56 ` syzbot [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=69ad8e15.050a0220.310d8.000d.GAE@google.com \
--to=syzbot+f2fbf7478a35a94c8b7c@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hpa@zytor.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=wireguard@lists.zx2c4.com \
--cc=x86@kernel.org \
/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®