syzbot |
sign-in | mailing list | source | docs |
====================================================== WARNING: possible circular locking dependency detected 5.15.171-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.760/7103 is trying to acquire lock: ffff88802bf25d18 (&disk->open_mutex){+.+.}-{3:3}, at: bd_register_pending_holders+0x33/0x320 block/holder.c:161 but task is already holding lock: ffffffff8cef8788 (major_names_lock){+.+.}-{3:3}, at: blk_request_module+0x2f/0x1a0 block/genhd.c:677 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #8 (major_names_lock){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 blk_request_module+0x2f/0x1a0 block/genhd.c:677 blkdev_get_no_open+0x39/0x190 block/bdev.c:740 blkdev_get_by_dev+0x89/0xa50 block/bdev.c:804 swsusp_check+0xb1/0x2c0 kernel/power/swap.c:1526 software_resume+0xc6/0x3c0 kernel/power/hibernate.c:977 resume_store+0xe3/0x130 kernel/power/hibernate.c:1179 kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2174 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0xacd/0xe50 fs/read_write.c:594 ksys_write+0x1a2/0x2c0 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #7 (system_transition_mutex/1){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 software_resume+0x7c/0x3c0 kernel/power/hibernate.c:932 resume_store+0xe3/0x130 kernel/power/hibernate.c:1179 kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2174 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0xacd/0xe50 fs/read_write.c:594 ksys_write+0x1a2/0x2c0 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #6 (&of->mutex){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 kernfs_seq_start+0x50/0x3b0 fs/kernfs/file.c:112 seq_read_iter+0x3d0/0xd10 fs/seq_file.c:225 call_read_iter include/linux/fs.h:2168 [inline] new_sync_read fs/read_write.c:404 [inline] vfs_read+0xa93/0xe10 fs/read_write.c:485 ksys_read+0x1a2/0x2c0 fs/read_write.c:623 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #5 (&p->lock){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 seq_read_iter+0xae/0xd10 fs/seq_file.c:182 call_read_iter include/linux/fs.h:2168 [inline] generic_file_splice_read+0x4ad/0x790 fs/splice.c:311 do_splice_to fs/splice.c:796 [inline] splice_direct_to_actor+0x448/0xc10 fs/splice.c:870 do_splice_direct+0x285/0x3d0 fs/splice.c:979 do_sendfile+0x622/0x1000 fs/read_write.c:1249 __do_sys_sendfile64 fs/read_write.c:1317 [inline] __se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1303 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #4 (sb_writers#3){.+.+}-{0:0}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1813 [inline] sb_start_write include/linux/fs.h:1883 [inline] file_start_write include/linux/fs.h:3044 [inline] lo_write_bvec+0x1a3/0x740 drivers/block/loop.c:315 lo_write_simple drivers/block/loop.c:338 [inline] do_req_filebacked drivers/block/loop.c:656 [inline] loop_handle_cmd drivers/block/loop.c:2234 [inline] loop_process_work+0x2309/0x2af0 drivers/block/loop.c:2274 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457 kthread+0x3f6/0x4f0 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #3 ((work_completion)(&worker->work)){+.+.}-{0:0}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 process_one_work+0x7f1/0x10c0 kernel/workqueue.c:2286 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457 kthread+0x3f6/0x4f0 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #2 ((null)){+.+.}-{0:0}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 flush_workqueue+0x170/0x1610 kernel/workqueue.c:2830 drain_workqueue+0xc5/0x390 kernel/workqueue.c:2995 destroy_workqueue+0x7b/0xae0 kernel/workqueue.c:4439 __loop_clr_fd+0x241/0xbe0 drivers/block/loop.c:1383 blkdev_put_whole block/bdev.c:692 [inline] blkdev_put+0x455/0x790 block/bdev.c:954 deactivate_locked_super+0xa0/0x110 fs/super.c:335 cleanup_mnt+0x44e/0x500 fs/namespace.c:1143 task_work_run+0x129/0x1a0 kernel/task_work.c:188 tracehook_notify_resume include/linux/tracehook.h:189 [inline] exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline] syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (&lo->lo_mutex){+.+.}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_killable_nested+0x17/0x20 kernel/locking/mutex.c:758 lo_open+0x68/0x100 drivers/block/loop.c:2055 blkdev_get_whole+0x94/0x390 block/bdev.c:669 blkdev_get_by_dev+0x2bc/0xa50 block/bdev.c:824 blkdev_open+0x138/0x2d0 block/fops.c:463 do_dentry_open+0x807/0xfb0 fs/open.c:826 do_open fs/namei.c:3608 [inline] path_openat+0x2705/0x2f20 fs/namei.c:3742 do_filp_open+0x21c/0x460 fs/namei.c:3769 do_sys_openat2+0x13b/0x4f0 fs/open.c:1253 do_sys_open fs/open.c:1269 [inline] __do_sys_openat fs/open.c:1285 [inline] __se_sys_openat fs/open.c:1280 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1280 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&disk->open_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 bd_register_pending_holders+0x33/0x320 block/holder.c:161 device_add_disk+0x59f/0xd10 block/genhd.c:482 add_disk include/linux/genhd.h:200 [inline] brd_alloc+0x4e6/0x720 drivers/block/brd.c:425 blk_request_module+0x181/0x1a0 block/genhd.c:680 blkdev_get_no_open+0x39/0x190 block/bdev.c:740 blkdev_get_by_dev+0x89/0xa50 block/bdev.c:804 swsusp_check+0xb1/0x2c0 kernel/power/swap.c:1526 software_resume+0xc6/0x3c0 kernel/power/hibernate.c:977 resume_store+0xe3/0x130 kernel/power/hibernate.c:1179 kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2174 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0xacd/0xe50 fs/read_write.c:594 ksys_write+0x1a2/0x2c0 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: &disk->open_mutex --> system_transition_mutex/1 --> major_names_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(major_names_lock); lock(system_transition_mutex/1); lock(major_names_lock); lock(&disk->open_mutex); *** DEADLOCK *** 6 locks held by syz.0.760/7103: #0: ffff8880785305f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2cb/0x380 fs/file.c:1057 #1: ffff88807ecc0460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x29a/0xe50 fs/read_write.c:590 #2: ffff888063588088 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e7/0x4f0 fs/kernfs/file.c:287 #3: ffff888144bfd830 (kn->active#817){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x20b/0x4f0 fs/kernfs/file.c:288 #4: ffffffff8c7d8788 (system_transition_mutex/1){+.+.}-{3:3}, at: software_resume+0x7c/0x3c0 kernel/power/hibernate.c:932 #5: ffffffff8cef8788 (major_names_lock){+.+.}-{3:3}, at: blk_request_module+0x2f/0x1a0 block/genhd.c:677 stack backtrace: CPU: 1 PID: 7103 Comm: syz.0.760 Not tainted 5.15.171-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 bd_register_pending_holders+0x33/0x320 block/holder.c:161 device_add_disk+0x59f/0xd10 block/genhd.c:482 add_disk include/linux/genhd.h:200 [inline] brd_alloc+0x4e6/0x720 drivers/block/brd.c:425 blk_request_module+0x181/0x1a0 block/genhd.c:680 blkdev_get_no_open+0x39/0x190 block/bdev.c:740 blkdev_get_by_dev+0x89/0xa50 block/bdev.c:804 swsusp_check+0xb1/0x2c0 kernel/power/swap.c:1526 software_resume+0xc6/0x3c0 kernel/power/hibernate.c:977 resume_store+0xe3/0x130 kernel/power/hibernate.c:1179 kernfs_fop_write_iter+0x3a2/0x4f0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2174 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0xacd/0xe50 fs/read_write.c:594 ksys_write+0x1a2/0x2c0 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f152dee2719 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f152c318038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f152e09a130 RCX: 00007f152dee2719 RDX: 0000000000000012 RSI: 0000000020000040 RDI: 0000000000000003 RBP: 00007f152df5539e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000001 R14: 00007f152e09a130 R15: 00007ffc02ed8118 </TASK> PM: Image not found (code -22)
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2024/11/11 22:42 | linux-5.15.y | 3c17fc483905 | 0c4b1325 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/11/01 13:02 | linux-5.15.y | 72244eab0dad | 96eb609f | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/10/30 18:45 | linux-5.15.y | 74cdd62cb470 | fb888278 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/10/28 03:19 | linux-5.15.y | 74cdd62cb470 | 65e8686b | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/10/24 17:30 | linux-5.15.y | 74cdd62cb470 | 0d144d1a | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/10/17 22:48 | linux-5.15.y | 584a40a22cb9 | 666f77ed | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/10/10 03:59 | linux-5.15.y | 3a5928702e71 | 0278d004 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/08/06 17:01 | linux-5.15.y | 7e89efd3ae1c | 1ef9fe42 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/08/01 01:00 | linux-5.15.y | 7e89efd3ae1c | 1e9c4cf3 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/07/31 22:50 | linux-5.15.y | 7e89efd3ae1c | 1e9c4cf3 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/07/18 16:35 | linux-5.15.y | 7c6d66f0266f | 71884c12 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/07/16 14:50 | linux-5.15.y | f45bea23c39c | b66b37bd | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/04/24 17:19 | linux-5.15.y | c52b9710c83d | 8bdc0f22 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders | ||
2024/04/15 01:51 | linux-5.15.y | fa3df276cd36 | c8349e48 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in bd_register_pending_holders |