REISERFS (device loop1): checking transaction log (loop1) REISERFS (device loop1): Using r5 hash to sort names REISERFS (device loop1): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc8-syzkaller-00148-g0d1409e4ff08 #0 Not tainted ------------------------------------------------------ syz-executor.1/3906 is trying to acquire lock: ffffc900058110f0 (&journal->j_mutex){+.+.}-{3:3}, at: reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline] ffffc900058110f0 (&journal->j_mutex){+.+.}-{3:3}, at: lock_journal fs/reiserfs/journal.c:534 [inline] ffffc900058110f0 (&journal->j_mutex){+.+.}-{3:3}, at: do_journal_begin_r+0x340/0x1070 fs/reiserfs/journal.c:3047 but task is already holding lock: ffff88807bf64460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#14){.+.+}-{0:0}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1826 [inline] sb_start_write+0x4d/0x1a0 include/linux/fs.h:1901 mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437 reiserfs_ioctl+0x16e/0x340 fs/reiserfs/ioctl.c:103 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&sbi->lock){+.+.}-{3:3}: lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 reiserfs_write_lock_nested+0x5b/0xd0 fs/reiserfs/lock.c:78 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:815 [inline] lock_journal fs/reiserfs/journal.c:534 [inline] do_journal_begin_r+0x34b/0x1070 fs/reiserfs/journal.c:3047 journal_begin+0x14b/0x350 fs/reiserfs/journal.c:3255 reiserfs_fill_super+0x172b/0x24a0 fs/reiserfs/super.c:2104 mount_bdev+0x26c/0x3a0 fs/super.c:1401 legacy_get_tree+0xea/0x180 fs/fs_context.c:610 vfs_get_tree+0x88/0x270 fs/super.c:1531 do_new_mount+0x289/0xad0 fs/namespace.c:3040 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&journal->j_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline] lock_journal fs/reiserfs/journal.c:534 [inline] do_journal_begin_r+0x340/0x1070 fs/reiserfs/journal.c:3047 journal_begin+0x14b/0x350 fs/reiserfs/journal.c:3255 reiserfs_dirty_inode+0x108/0x230 fs/reiserfs/super.c:710 __mark_inode_dirty+0x1e7/0x600 fs/fs-writeback.c:2408 mark_inode_dirty include/linux/fs.h:2475 [inline] reiserfs_ioctl+0x293/0x340 fs/reiserfs/ioctl.c:111 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 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#14 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#14); lock(&sbi->lock); lock(sb_writers#14); lock(&journal->j_mutex); *** DEADLOCK *** 1 lock held by syz-executor.1/3906: #0: ffff88807bf64460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437 stack backtrace: CPU: 1 PID: 3906 Comm: syz-executor.1 Not tainted 6.1.0-rc8-syzkaller-00148-g0d1409e4ff08 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 check_noncircular+0x2cc/0x390 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain+0x1898/0x6ae0 kernel/locking/lockdep.c:3831 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055 lock_acquire+0x182/0x3c0 kernel/locking/lockdep.c:5668 __mutex_lock_common+0x1bd/0x26e0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:814 [inline] lock_journal fs/reiserfs/journal.c:534 [inline] do_journal_begin_r+0x340/0x1070 fs/reiserfs/journal.c:3047 journal_begin+0x14b/0x350 fs/reiserfs/journal.c:3255 reiserfs_dirty_inode+0x108/0x230 fs/reiserfs/super.c:710 __mark_inode_dirty+0x1e7/0x600 fs/fs-writeback.c:2408 mark_inode_dirty include/linux/fs.h:2475 [inline] reiserfs_ioctl+0x293/0x340 fs/reiserfs/ioctl.c:111 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f856388c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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:00007f8564623168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f85639abf80 RCX: 00007f856388c0d9 RDX: 0000000020000040 RSI: 0000000040087602 RDI: 0000000000000003 RBP: 00007f85638e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd3dac08df R14: 00007f8564623300 R15: 0000000000022000