Hello, syzbot found the following issue on: HEAD commit: 2ab795141095 Merge tag 'cxl-fixes-6.10-rc3' of git://git.k.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1671b2f2980000 kernel config: https://syzkaller.appspot.com/x/.config?x=f0e2e3f7ede77526 dashboard link: https://syzkaller.appspot.com/bug?extid=abba31ed4fc4178349e9 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/613f40485ad9/disk-2ab79514.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/5f6673b48420/vmlinux-2ab79514.xz kernel image: https://storage.googleapis.com/syzbot-assets/9659affc7dfc/bzImage-2ab79514.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+abba31ed4fc4178349e9@xxxxxxxxxxxxxxxxxxxxxxxxx INFO: task kworker/u8:2:35 blocked for more than 143 seconds. Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u8:2 state:D stack:23032 pid:35 tgid:35 ppid:2 flags:0x00004000 Workqueue: netns cleanup_net Call Trace: <TASK> context_switch kernel/sched/core.c:5408 [inline] __schedule+0x17e8/0x4a20 kernel/sched/core.c:6745 __schedule_loop kernel/sched/core.c:6822 [inline] schedule+0x14b/0x320 kernel/sched/core.c:6837 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6894 __mutex_lock_common kernel/locking/mutex.c:684 [inline] __mutex_lock+0x6a4/0xd70 kernel/locking/mutex.c:752 wiphy_unregister+0x236/0xaa0 net/wireless/core.c:1096 ieee80211_unregister_hw+0x1e2/0x2c0 net/mac80211/main.c:1675 mac80211_hwsim_del_radio+0x2c2/0x4c0 drivers/net/wireless/virtual/mac80211_hwsim.c:5576 hwsim_exit_net+0x5c1/0x670 drivers/net/wireless/virtual/mac80211_hwsim.c:6453 ops_exit_list net/core/net_namespace.c:173 [inline] cleanup_net+0x804/0xcc0 net/core/net_namespace.c:640 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2e/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd70 kernel/workqueue.c:3393 kthread+0x2f2/0x390 kernel/kthread.c:389 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> INFO: task dhcpcd:4754 blocked for more than 144 seconds. Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:dhcpcd state:D stack:20384 pid:4754 tgid:4754 ppid:4753 flags:0x00000002 Call Trace: <TASK> context_switch kernel/sched/core.c:5408 [inline] __schedule+0x17e8/0x4a20 kernel/sched/core.c:6745 __schedule_loop kernel/sched/core.c:6822 [inline] schedule+0x14b/0x320 kernel/sched/core.c:6837 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6894 __mutex_lock_common kernel/locking/mutex.c:684 [inline] __mutex_lock+0x6a4/0xd70 kernel/locking/mutex.c:752 devinet_ioctl+0x2ce/0x1bc0 net/ipv4/devinet.c:1101 inet_ioctl+0x3d7/0x4f0 net/ipv4/af_inet.c:1003 sock_do_ioctl+0x15a/0x460 net/socket.c:1222 sock_ioctl+0x629/0x8e0 net/socket.c:1341 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfe/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2f49d5ed49 RSP: 002b:00007ffe50118268 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f2f49c906c0 RCX: 00007f2f49d5ed49 RDX: 00007ffe50128458 RSI: 0000000000008914 RDI: 0000000000000011 RBP: 00007ffe50138618 R08: 00007ffe50128418 R09: 00007ffe501283c8 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe50128458 R14: 0000000000000028 R15: 0000000000008914 </TASK> INFO: task kworker/0:7:5217 blocked for more than 144 seconds. Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/0:7 state:D stack:19376 pid:5217 --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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
