REISERFS (device loop0): Using rupasov hash to sort names REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.2.0-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/5597 is trying to acquire lock: ffffc90004cc10f0 (&journal->j_mutex){+.+.}-{3:3}, at: do_journal_begin_r+0x301/0xdc0 but task is already holding lock: ffff88807e866460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write_file+0x5b/0x1a0 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#13){.+.+}-{0:0}: lock_acquire+0x214/0x600 sb_start_write+0x47/0x130 mnt_want_write_file+0x5b/0x1a0 reiserfs_ioctl+0x149/0x2c0 __se_sys_ioctl+0xa7/0xf0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&sbi->lock){+.+.}-{3:3}: lock_acquire+0x214/0x600 __mutex_lock_common+0x1c2/0x2630 mutex_lock_nested+0x1b/0x20 reiserfs_write_lock_nested+0x4a/0xb0 do_journal_begin_r+0x30c/0xdc0 journal_begin+0x13f/0x2f0 reiserfs_fill_super+0x1483/0x20e0 mount_bdev+0x27f/0x370 legacy_get_tree+0xe9/0x170 vfs_get_tree+0x7f/0x220 do_new_mount+0x1e5/0x940 __se_sys_mount+0x20d/0x2a0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&journal->j_mutex){+.+.}-{3:3}: validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x214/0x600 __mutex_lock_common+0x1c2/0x2630 mutex_lock_nested+0x1b/0x20 do_journal_begin_r+0x301/0xdc0 journal_begin+0x13f/0x2f0 reiserfs_dirty_inode+0xf6/0x200 __mark_inode_dirty+0x279/0xc70 reiserfs_ioctl+0x210/0x2c0 __se_sys_ioctl+0xa7/0xf0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &journal->j_mutex --> &sbi->lock --> sb_writers#13 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#13); lock(&sbi->lock); lock(sb_writers#13); lock(&journal->j_mutex); *** DEADLOCK *** 1 lock held by syz-executor.0/5597: #0: ffff88807e866460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write_file+0x5b/0x1a0 stack backtrace: CPU: 1 PID: 5597 Comm: syz-executor.0 Not tainted 6.2.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: dump_stack_lvl+0x12e/0x1d0 check_noncircular+0x2d1/0x390 validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x214/0x600 __mutex_lock_common+0x1c2/0x2630 mutex_lock_nested+0x1b/0x20 do_journal_begin_r+0x301/0xdc0 journal_begin+0x13f/0x2f0 reiserfs_dirty_inode+0xf6/0x200 __mark_inode_dirty+0x279/0xc70 reiserfs_ioctl+0x210/0x2c0 __se_sys_ioctl+0xa7/0xf0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f612748b639 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f61281d9168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f61275abf80 RCX: 00007f612748b639 RDX: 0000000020000080 RSI: 0000000040087602 RDI: 0000000000000006 RBP: 00007f61274e6ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd18ca4ebf R14: 00007f61281d9300 R15: 0000000000022000