Hello, syzbot found the following issue on: HEAD commit: 6fbf71854e2d Merge tag 'perf-tools-fixes-for-v6.10-1-2024-.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15b4942c980000 kernel config: https://syzkaller.appspot.com/x/.config?x=ee7b962709a5f5a5 dashboard link: https://syzkaller.appspot.com/bug?extid=5c6179f2c4f1e111df11 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/91effa72f285/disk-6fbf7185.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c6afe2efff99/vmlinux-6fbf7185.xz kernel image: https://storage.googleapis.com/syzbot-assets/46aae93f5511/bzImage-6fbf7185.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+5c6179f2c4f1e111df11@xxxxxxxxxxxxxxxxxxxxxxxxx INFO: task udevd:16174 blocked for more than 143 seconds. Not tainted 6.9.0-syzkaller-12400-g6fbf71854e2d #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:udevd state:D stack:23920 pid:16174 tgid:16174 ppid:1 flags:0x00000002 Call Trace: <TASK> context_switch kernel/sched/core.c:5408 [inline] __schedule+0x1796/0x49d0 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 bdev_open+0xe5/0xc60 block/bdev.c:897 blkdev_open+0x20d/0x2e0 block/fops.c:615 do_dentry_open+0x95a/0x1720 fs/open.c:955 do_open fs/namei.c:3650 [inline] path_openat+0x289f/0x3280 fs/namei.c:3807 do_filp_open+0x235/0x490 fs/namei.c:3834 do_sys_openat2+0x13e/0x1d0 fs/open.c:1405 do_sys_open fs/open.c:1420 [inline] __do_sys_openat fs/open.c:1436 [inline] __se_sys_openat fs/open.c:1431 [inline] __x64_sys_openat+0x247/0x2a0 fs/open.c:1431 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:0x7f7f09b169a4 RSP: 002b:00007fffaaf9cc90 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 000055bf84d3cdb0 RCX: 00007f7f09b169a4 RDX: 00000000000a0800 RSI: 000055bf84d19770 RDI: 00000000ffffff9c RBP: 000055bf84d19770 R08: 0000000000000001 R09: 7fffffffffffffff R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000a0800 R13: 000055bf84d2b2c0 R14: 0000000000000001 R15: 000055bf84d18910 </TASK> INFO: task syz-executor.1:16345 blocked for more than 143 seconds. Not tainted 6.9.0-syzkaller-12400-g6fbf71854e2d #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.1 state:D stack:21168 pid:16345 tgid:16344 ppid:15599 flags:0x00004006 Call Trace: <TASK> context_switch kernel/sched/core.c:5408 [inline] __schedule+0x1796/0x49d0 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 bdev_release+0x184/0x700 block/bdev.c:1080 blkdev_release+0x15/0x20 block/fops.c:623 __fput+0x406/0x8b0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:180 get_signal+0x15e6/0x1740 kernel/signal.c:2681 arch_do_signal_or_restart+0x96/0x860 arch/x86/kernel/signal.c:310 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0xc9/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f297527cee9 RSP: 002b:00007f297608b0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: 0000000000000000 RBX: 00007f29753abf80 RCX: 00007f297527cee9 RDX: 0000000000000000 RSI: 000000000000ab03 RDI: 0000000000000006 RBP: 00007f29752c949e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f29753abf80 R15: 00007ffd34ac6de8 </TASK> INFO: task syz-executor.1:16353 blocked for more than 144 seconds. Not tainted 6.9.0-syzkaller-12400-g6fbf71854e2d #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-executor.1 state:D stack:18712 pid:16353 tgid:16344 ppid:15599 flags:0x00004006 Call Trace: <TASK> context_switch kernel/sched/core.c:5408 [inline] __schedule+0x1796/0x49d0 kernel/sched/core.c:6745 --- 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
