[v5.15] INFO: task hung in linkwatch_event
0 views
Skip to first unread message
syzbot
Jan 11, 2024, 6:32:26 AMJan 11
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=150088a5e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=dc70d39e176dd118
dashboard link: https://syzkaller.appspot.com/bug?extid=07cfae8a92c0b83c91de
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/e52ed2e53c97/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0baec14a2844/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d33fddfbaf83/bzImage-26c690ef.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+07cfae...@syzkaller.appspotmail.com
INFO: task kworker/1:0:21 blocked for more than 143 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0 state:D stack:23232 pid: 21 ppid: 2 flags:0x00004000
Workqueue: events linkwatch_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
linkwatch_event+0xa/0x50 net/core/link_watch.c:251
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task kworker/0:23:18143 blocked for more than 144 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:23 state:D stack:25280 pid:18143 ppid: 2 flags:0x00004000
Workqueue: events switchdev_deferred_process_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task syz-executor.4:18522 blocked for more than 144 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:20568 pid:18522 ppid: 18100 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tun_detach drivers/net/tun.c:698 [inline]
tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314
exc_general_protection+0x358/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:562
RIP: 0033:0x7f931b7f6d31
RSP: 002b:00000000200000c0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f931b926120 RCX: 00007f931b7f6d29
RDX: 0000000020000100 RSI: 00000000200000c0 RDI: 0000000000002000
RBP: 00007f931b84347a R08: 0000000020000180 R09: 0000000020000180
R10: 0000000020000140 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000006e R14: 00007f931b926120 R15: 00007fff34a71978
</TASK>
INFO: task syz-executor.0:18593 blocked for more than 146 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:20416 pid:18593 ppid: 18155 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tun_detach drivers/net/tun.c:698 [inline]
tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314
exc_general_protection+0x358/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:562
RIP: 0033:0x7ffb3e29ed31
RSP: 002b:00000000200000c0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007ffb3e3cdf80 RCX: 00007ffb3e29ed29
RDX: 0000000020000100 RSI: 00000000200000c0 RDI: 0000000000002000
RBP: 00007ffb3e2eb47a R08: 0000000020000180 R09: 0000000020000180
R10: 0000000020000140 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000000b R14: 00007ffb3e3cdf80 R15: 00007ffdc7299df8
</TASK>
Showing all locks held in the system:
3 locks held by kworker/1:0/21:
#0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90000db7d20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
1 lock held by khungtaskd/27:
#0: ffffffff8c91f220 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/u4:3/1162:
#0: ffff888011dcd138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900057cfd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9ce7d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:558
#3: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock_unregistering net/core/dev.c:11576 [inline]
#3: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: default_device_exit_batch+0x1ac/0x3f0 net/core/dev.c:11614
#4: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#4: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
2 locks held by getty/3258:
#0: ffff888023d11098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900024b32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/3569:
#0: ffff888011c71d38 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc9000493fd20 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x7f/0xb70 net/wireless/reg.c:2436
3 locks held by kworker/1:6/3572:
#0: ffff88814a882938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc9000496fd20 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4640
5 locks held by kworker/u4:7/4945:
#0: ffff888014394938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90005327d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffff8880256220e0 (&type->s_umount_key#32){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418
#3: ffff888025624bd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1f6/0x3d10 fs/ext4/inode.c:2677
#4: ffff888025626990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x12b9/0x1570 fs/jbd2/transaction.c:462
3 locks held by kworker/u4:9/8142:
3 locks held by kworker/0:23/18143:
#0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900033d7d20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
2 locks held by kworker/0:24/18147:
#0: ffff888011c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900033e7d20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
1 lock held by syz-executor.4/18522:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
1 lock held by syz-executor.0/18593:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
2 locks held by syz-executor.3/18838:
1 lock held by syz-executor.0/18854:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.3/18861:
1 lock held by syz-executor.3/18874:
3 locks held by syz-executor.5/18878:
1 lock held by syz-executor.5/18893:
3 locks held by syz-executor.5/18900:
2 locks held by syz-executor.5/18917:
2 locks held by syz-executor.3/18920:
3 locks held by syz-executor.5/18935:
3 locks held by syz-executor.5/18946:
2 locks held by syz-executor.5/18956:
1 lock held by syz-executor.4/18971:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.3/19014:
2 locks held by syz-executor.1/19016:
1 lock held by syz-executor.0/19038:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.1/19079:
1 lock held by syz-executor.4/19149:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
3 locks held by syz-executor.2/19171:
1 lock held by syz-executor.5/19180:
2 locks held by syz-executor.2/19184:
2 locks held by syz-executor.1/19185:
2 locks held by syz-executor.3/19187:
2 locks held by syz-executor.2/19191:
3 locks held by syz-executor.1/19198:
2 locks held by syz-executor.2/19203:
3 locks held by syz-executor.3/19206:
2 locks held by syz-executor.5/19207:
2 locks held by syz-executor.1/19212:
2 locks held by syz-executor.2/19215:
1 lock held by syz-executor.3/19223:
3 locks held by syz-executor.5/19227:
2 locks held by syz-executor.1/19229:
2 locks held by syz-executor.2/19230:
1 lock held by syz-executor.0/19232:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
2 locks held by syz-executor.2/19240:
2 locks held by syz-executor.5/19244:
3 locks held by syz-executor.1/19246:
2 locks held by syz-executor.2/19254:
3 locks held by syz-executor.1/19257:
2 locks held by syz-executor.3/19258:
2 locks held by syz-executor.5/19264:
2 locks held by syz-executor.1/19272:
3 locks held by syz-executor.3/19273:
2 locks held by syz-executor.2/19275:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2591 Comm: kworker/u4:4 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: 0x0 (phy90)
RIP: 0010:div_u64_rem include/linux/math64.h:29 [inline]
RIP: 0010:div_u64 include/linux/math64.h:128 [inline]
RIP: 0010:___update_load_avg kernel/sched/pelt.c:268 [inline]
RIP: 0010:__update_load_avg_cfs_rq+0x592/0xb40 kernel/sched/pelt.c:331
Code: 24 9c 00 00 00 80 3c 30 00 74 0f e8 08 52 69 00 48 be 00 00 00 00 00 fc ff df 49 8b 84 24 88 00 00 00 44 89 f5 31 d2 48 f7 f5 <48> 89 c3 49 8d bc 24 a0 00 00 00 48 89 f8 48 c1 e8 03 80 3c 30 00
RSP: 0018:ffffc9000bbb7a00 EFLAGS: 00000046
RAX: 0000000000000fff RBX: ffff888014580890 RCX: 0000000000001000
RDX: 000000000000437c RSI: dffffc0000000000 RDI: ffff888014580888
RBP: 000000000000b7b1 R08: 0000000000000533 R09: 0000000000000001
R10: 000000000b98982d R11: dffffc0000000001 R12: ffff888014580800
R13: 000000000000021a R14: 000000000000b7b1 R15: 0000000000001000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f58a0bd9440 CR3: 0000000078ca0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
update_cfs_rq_load_avg kernel/sched/fair.c:3765 [inline]
update_load_avg+0x513/0x1110 kernel/sched/fair.c:3879
set_next_entity+0x2b3/0x580 kernel/sched/fair.c:4679
pick_next_task_fair+0x43a/0x9c0 kernel/sched/fair.c:7564
__pick_next_task kernel/sched/core.c:5650 [inline]
pick_next_task kernel/sched/core.c:5758 [inline]
__schedule+0x86d/0x45b0 kernel/sched/core.c:6340
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
worker_thread+0xf56/0x1280 kernel/workqueue.c:2478
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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 syzk...@googlegroups.com.
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 found the following issue on:
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=150088a5e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=dc70d39e176dd118
dashboard link: https://syzkaller.appspot.com/bug?extid=07cfae8a92c0b83c91de
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/e52ed2e53c97/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0baec14a2844/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d33fddfbaf83/bzImage-26c690ef.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+07cfae...@syzkaller.appspotmail.com
INFO: task kworker/1:0:21 blocked for more than 143 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0 state:D stack:23232 pid: 21 ppid: 2 flags:0x00004000
Workqueue: events linkwatch_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
linkwatch_event+0xa/0x50 net/core/link_watch.c:251
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task kworker/0:23:18143 blocked for more than 144 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:23 state:D stack:25280 pid:18143 ppid: 2 flags:0x00004000
Workqueue: events switchdev_deferred_process_work
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
INFO: task syz-executor.4:18522 blocked for more than 144 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:20568 pid:18522 ppid: 18100 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tun_detach drivers/net/tun.c:698 [inline]
tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314
exc_general_protection+0x358/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:562
RIP: 0033:0x7f931b7f6d31
RSP: 002b:00000000200000c0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f931b926120 RCX: 00007f931b7f6d29
RDX: 0000000020000100 RSI: 00000000200000c0 RDI: 0000000000002000
RBP: 00007f931b84347a R08: 0000000020000180 R09: 0000000020000180
R10: 0000000020000140 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000006e R14: 00007f931b926120 R15: 00007fff34a71978
</TASK>
INFO: task syz-executor.0:18593 blocked for more than 146 seconds.
Not tainted 5.15.146-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0 state:D stack:20416 pid:18593 ppid: 18155 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
__mutex_lock_common+0xe34/0x25a0 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tun_detach drivers/net/tun.c:698 [inline]
tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
__fput+0x3bf/0x890 fs/file_table.c:280
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
get_signal+0xc66/0x14e0 kernel/signal.c:2889
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314
exc_general_protection+0x358/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:562
RIP: 0033:0x7ffb3e29ed31
RSP: 002b:00000000200000c0 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007ffb3e3cdf80 RCX: 00007ffb3e29ed29
RDX: 0000000020000100 RSI: 00000000200000c0 RDI: 0000000000002000
RBP: 00007ffb3e2eb47a R08: 0000000020000180 R09: 0000000020000180
R10: 0000000020000140 R11: 0000000000000206 R12: 0000000000000000
R13: 000000000000000b R14: 00007ffb3e3cdf80 R15: 00007ffdc7299df8
</TASK>
Showing all locks held in the system:
3 locks held by kworker/1:0/21:
#0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90000db7d20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
1 lock held by khungtaskd/27:
#0: ffffffff8c91f220 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/u4:3/1162:
#0: ffff888011dcd138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900057cfd20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9ce7d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf1/0xb60 net/core/net_namespace.c:558
#3: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock_unregistering net/core/dev.c:11576 [inline]
#3: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: default_device_exit_batch+0x1ac/0x3f0 net/core/dev.c:11614
#4: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#4: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
2 locks held by getty/3258:
#0: ffff888023d11098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900024b32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/3569:
#0: ffff888011c71d38 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc9000493fd20 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x7f/0xb70 net/wireless/reg.c:2436
3 locks held by kworker/1:6/3572:
#0: ffff88814a882938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc9000496fd20 ((addr_chk_work).work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0xa/0x20 net/ipv6/addrconf.c:4640
5 locks held by kworker/u4:7/4945:
#0: ffff888014394938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc90005327d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffff8880256220e0 (&type->s_umount_key#32){++++}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:418
#3: ffff888025624bd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1f6/0x3d10 fs/ext4/inode.c:2677
#4: ffff888025626990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x12b9/0x1570 fs/jbd2/transaction.c:462
3 locks held by kworker/u4:9/8142:
3 locks held by kworker/0:23/18143:
#0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900033d7d20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
2 locks held by kworker/0:24/18147:
#0: ffff888011c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc900033e7d20 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
1 lock held by syz-executor.4/18522:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
1 lock held by syz-executor.0/18593:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3a/0x1b0 drivers/net/tun.c:3434
2 locks held by syz-executor.3/18838:
1 lock held by syz-executor.0/18854:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.3/18861:
1 lock held by syz-executor.3/18874:
3 locks held by syz-executor.5/18878:
1 lock held by syz-executor.5/18893:
3 locks held by syz-executor.5/18900:
2 locks held by syz-executor.5/18917:
2 locks held by syz-executor.3/18920:
3 locks held by syz-executor.5/18935:
3 locks held by syz-executor.5/18946:
2 locks held by syz-executor.5/18956:
1 lock held by syz-executor.4/18971:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.3/19014:
2 locks held by syz-executor.1/19016:
1 lock held by syz-executor.0/19038:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
1 lock held by syz-executor.1/19079:
1 lock held by syz-executor.4/19149:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
3 locks held by syz-executor.2/19171:
1 lock held by syz-executor.5/19180:
2 locks held by syz-executor.2/19184:
2 locks held by syz-executor.1/19185:
2 locks held by syz-executor.3/19187:
2 locks held by syz-executor.2/19191:
3 locks held by syz-executor.1/19198:
2 locks held by syz-executor.2/19203:
3 locks held by syz-executor.3/19206:
2 locks held by syz-executor.5/19207:
2 locks held by syz-executor.1/19212:
2 locks held by syz-executor.2/19215:
1 lock held by syz-executor.3/19223:
3 locks held by syz-executor.5/19227:
2 locks held by syz-executor.1/19229:
2 locks held by syz-executor.2/19230:
1 lock held by syz-executor.0/19232:
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da4c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
2 locks held by syz-executor.2/19240:
2 locks held by syz-executor.5/19244:
3 locks held by syz-executor.1/19246:
2 locks held by syz-executor.2/19254:
3 locks held by syz-executor.1/19257:
2 locks held by syz-executor.3/19258:
2 locks held by syz-executor.5/19264:
2 locks held by syz-executor.1/19272:
3 locks held by syz-executor.3/19273:
2 locks held by syz-executor.2/19275:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2591 Comm: kworker/u4:4 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Workqueue: 0x0 (phy90)
RIP: 0010:div_u64_rem include/linux/math64.h:29 [inline]
RIP: 0010:div_u64 include/linux/math64.h:128 [inline]
RIP: 0010:___update_load_avg kernel/sched/pelt.c:268 [inline]
RIP: 0010:__update_load_avg_cfs_rq+0x592/0xb40 kernel/sched/pelt.c:331
Code: 24 9c 00 00 00 80 3c 30 00 74 0f e8 08 52 69 00 48 be 00 00 00 00 00 fc ff df 49 8b 84 24 88 00 00 00 44 89 f5 31 d2 48 f7 f5 <48> 89 c3 49 8d bc 24 a0 00 00 00 48 89 f8 48 c1 e8 03 80 3c 30 00
RSP: 0018:ffffc9000bbb7a00 EFLAGS: 00000046
RAX: 0000000000000fff RBX: ffff888014580890 RCX: 0000000000001000
RDX: 000000000000437c RSI: dffffc0000000000 RDI: ffff888014580888
RBP: 000000000000b7b1 R08: 0000000000000533 R09: 0000000000000001
R10: 000000000b98982d R11: dffffc0000000001 R12: ffff888014580800
R13: 000000000000021a R14: 000000000000b7b1 R15: 0000000000001000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f58a0bd9440 CR3: 0000000078ca0000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
update_cfs_rq_load_avg kernel/sched/fair.c:3765 [inline]
update_load_avg+0x513/0x1110 kernel/sched/fair.c:3879
set_next_entity+0x2b3/0x580 kernel/sched/fair.c:4679
pick_next_task_fair+0x43a/0x9c0 kernel/sched/fair.c:7564
__pick_next_task kernel/sched/core.c:5650 [inline]
pick_next_task kernel/sched/core.c:5758 [inline]
__schedule+0x86d/0x45b0 kernel/sched/core.c:6340
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
worker_thread+0xf56/0x1280 kernel/workqueue.c:2478
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
---
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 syzk...@googlegroups.com.
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
Reply all
Reply to author
Forward
0 new messages