[v6.1] INFO: task hung in ip_tunnel_init_net (2)

0 views
Skip to first unread message

syzbot

unread,
Dec 5, 2024, 4:31:27 PM12/5/24
Hello,

syzbot found the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1479a8df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5516a02be29a5649
dashboard link: https://syzkaller.appspot.com/bug?extid=5e3915d42e84afc822b5
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0c036f68ae30/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2f9e8d0497b5/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47a62df8c4f9/bzImage-e4d90d63.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

INFO: task syz-executor:7519 blocked for more than 143 seconds.
Not tainted 6.1.119-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22760 pid:7519 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x143f/0x4570 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6693
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x6b9/0xd80 kernel/locking/mutex.c:747
ip_tunnel_init_net+0x20f/0x700 net/ipv4/ip_tunnel.c:1099
ops_init+0x35d/0x610 net/core/net_namespace.c:138
setup_net+0x4b5/0xb90 net/core/net_namespace.c:335
copy_net_ns+0x392/0x5d0 net/core/net_namespace.c:481
create_new_namespaces+0x425/0x7a0 kernel/nsproxy.c:110
unshare_nsproxy_namespaces+0x11e/0x170 kernel/nsproxy.c:226
ksys_unshare+0x531/0xa40 kernel/fork.c:3201
__do_sys_unshare kernel/fork.c:3272 [inline]
__se_sys_unshare kernel/fork.c:3270 [inline]
__x64_sys_unshare+0x34/0x40 kernel/fork.c:3270
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at [email protected].

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Mar 15, 2025, 4:31:15 PMMar 15
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages