EXT4-fs (loop0): Mount option "delalloc" incompatible with ext2 ====================================================== WARNING: possible circular locking dependency detected 5.15.189-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.1001/7681 is trying to acquire lock: ffff8880228bb938 ((wq_completion)loop0){+.+.}-{0:0}, at: flush_workqueue+0x126/0x1380 kernel/workqueue.c:2830 but task is already holding lock: ffff888147440468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #6 (&lo->lo_mutex){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 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+0x6a/0x100 drivers/block/loop.c:2056 blkdev_get_whole+0x90/0x390 block/bdev.c:669 blkdev_get_by_dev+0x2d0/0xa60 block/bdev.c:827 blkdev_open+0x12d/0x2c0 block/fops.c:466 do_dentry_open+0x7ff/0xf80 fs/open.c:826 do_open fs/namei.c:3608 [inline] path_openat+0x2682/0x2f30 fs/namei.c:3742 do_filp_open+0x1b3/0x3e0 fs/namei.c:3769 do_sys_openat2+0x142/0x4a0 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+0x135/0x160 fs/open.c:1280 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #5 (&disk->open_mutex){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820 swsusp_check+0x9b/0x2a0 kernel/power/swap.c:1526 software_resume+0xc6/0x3b0 kernel/power/hibernate.c:982 resume_store+0xe4/0x130 kernel/power/hibernate.c:1184 kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x712/0xd00 fs/read_write.c:594 ksys_write+0x14d/0x250 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #4 (system_transition_mutex/1){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 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/0x3b0 kernel/power/hibernate.c:937 resume_store+0xe4/0x130 kernel/power/hibernate.c:1184 kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x712/0xd00 fs/read_write.c:594 ksys_write+0x14d/0x250 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #3 (&of->mutex){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 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+0x51/0x3c0 fs/kernfs/file.c:112 seq_read_iter+0x3c4/0xd50 fs/seq_file.c:225 call_read_iter include/linux/fs.h:2166 [inline] new_sync_read fs/read_write.c:404 [inline] vfs_read+0x725/0xcf0 fs/read_write.c:485 ksys_read+0x14d/0x250 fs/read_write.c:623 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #2 (&p->lock){+.+.}-{3:3}: __mutex_lock_common+0x1eb/0x2390 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+0xad/0xd50 fs/seq_file.c:182 do_iter_readv_writev+0x497/0x600 fs/read_write.c:-1 do_iter_read+0x20b/0x7c0 fs/read_write.c:790 lo_read_simple drivers/block/loop.c:392 [inline] do_req_filebacked drivers/block/loop.c:663 [inline] loop_handle_cmd drivers/block/loop.c:2235 [inline] loop_process_work+0x18dc/0x2480 drivers/block/loop.c:2275 process_one_work+0x863/0x1000 kernel/workqueue.c:2310 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #1 ((work_completion)(&worker->work)){+.+.}-{0:0}: process_one_work+0x7bf/0x1000 kernel/workqueue.c:2286 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #0 ((wq_completion)loop0){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 flush_workqueue+0x142/0x1380 kernel/workqueue.c:2830 drain_workqueue+0xcf/0x380 kernel/workqueue.c:2995 destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439 __loop_clr_fd+0x234/0xb90 drivers/block/loop.c:1384 loop_clr_fd drivers/block/loop.c:1510 [inline] lo_ioctl+0xffa/0x1cf0 drivers/block/loop.c:1866 blkdev_ioctl+0x33c/0x690 block/ioctl.c:604 block_ioctl+0xac/0xf0 block/fops.c:496 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: (wq_completion)loop0 --> &disk->open_mutex --> &lo->lo_mutex Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&lo->lo_mutex); lock(&disk->open_mutex); lock(&lo->lo_mutex); lock((wq_completion)loop0); *** DEADLOCK *** 1 lock held by syz.0.1001/7681: #0: ffff888147440468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366 stack backtrace: CPU: 0 PID: 7681 Comm: syz.0.1001 Not tainted 5.15.189-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106 check_noncircular+0x274/0x310 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 kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623 flush_workqueue+0x142/0x1380 kernel/workqueue.c:2830 drain_workqueue+0xcf/0x380 kernel/workqueue.c:2995 destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439 __loop_clr_fd+0x234/0xb90 drivers/block/loop.c:1384 loop_clr_fd drivers/block/loop.c:1510 [inline] lo_ioctl+0xffa/0x1cf0 drivers/block/loop.c:1866 blkdev_ioctl+0x33c/0x690 block/ioctl.c:604 block_ioctl+0xac/0xf0 block/fops.c:496 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7fd517c8d7eb Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 RSP: 002b:00007fd515eb2e10 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: ffffffffffffffff RCX: 00007fd517c8d7eb RDX: 0000000000000000 RSI: 0000000000004c01 RDI: 000000000000000b RBP: 000000000000000b R08: 0000000000000000 R09: 0000000001810754 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000016 R13: 00007fd515eb2eb0 R14: 000000000000046e R15: 0000200000003640