====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/17611 is trying to acquire lock: 0000000073348759 (&journal->j_mutex){+.+.}, at: reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] 0000000073348759 (&journal->j_mutex){+.+.}, at: lock_journal fs/reiserfs/journal.c:538 [inline] 0000000073348759 (&journal->j_mutex){+.+.}, at: do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 but task is already holding lock: 000000003f125460 (sb_writers#25){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] 000000003f125460 (sb_writers#25){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#25){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 reiserfs_ioctl+0x1a7/0x9a0 fs/reiserfs/ioctl.c:110 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&sbi->lock){+.+.}: reiserfs_write_lock_nested+0x65/0xe0 fs/reiserfs/lock.c:78 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:817 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x2a2/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_fill_super+0x1a81/0x2d80 fs/reiserfs/super.c:2117 mount_bdev+0x2fc/0x3b0 fs/super.c:1158 mount_fs+0xa3/0x310 fs/super.c:1261 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961 vfs_kern_mount fs/namespace.c:951 [inline] do_new_mount fs/namespace.c:2492 [inline] do_mount+0x115c/0x2f50 fs/namespace.c:2822 ksys_mount+0xcf/0x130 fs/namespace.c:3038 __do_sys_mount fs/namespace.c:3052 [inline] __se_sys_mount fs/namespace.c:3049 [inline] __x64_sys_mount+0xba/0x150 fs/namespace.c:3049 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&journal->j_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_dirty_inode+0xff/0x250 fs/reiserfs/super.c:716 __mark_inode_dirty+0x16b/0x1140 fs/fs-writeback.c:2164 mark_inode_dirty include/linux/fs.h:2086 [inline] reiserfs_ioctl+0x7dc/0x9a0 fs/reiserfs/ioctl.c:118 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &journal->j_mutex --> &sbi->lock --> sb_writers#25 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#25); lock(&sbi->lock); lock(sb_writers#25); lock(&journal->j_mutex); *** DEADLOCK *** 1 lock held by syz-executor.4/17611: #0: 000000003f125460 (sb_writers#25){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 000000003f125460 (sb_writers#25){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 stack backtrace: CPU: 1 PID: 17611 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_dirty_inode+0xff/0x250 fs/reiserfs/super.c:716 __mark_inode_dirty+0x16b/0x1140 fs/fs-writeback.c:2164 mark_inode_dirty include/linux/fs.h:2086 [inline] reiserfs_ioctl+0x7dc/0x9a0 fs/reiserfs/ioctl.c:118 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7fe083eef5a9 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:00007fe082462168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe08400ff80 RCX: 00007fe083eef5a9 RDX: 0000000020000080 RSI: 0000000040087602 RDI: 0000000000000005 RBP: 00007fe083f4a7b0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff3a3d7c2f R14: 00007fe082462300 R15: 0000000000022000 nla_parse: 4 callbacks suppressed netlink: 24 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 120 bytes leftover after parsing attributes in process `syz-executor.5'. audit: type=1804 audit(1666917712.120:1479): pid=17805 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir1485160853/syzkaller.4PEQXG/231/bus" dev="sda1" ino=13901 res=1 XFS (loop4): Invalid superblock magic number audit: type=1804 audit(1666917712.320:1480): pid=17822 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir1485160853/syzkaller.4PEQXG/232/bus" dev="sda1" ino=14150 res=1 audit: type=1804 audit(1666917712.590:1481): pid=17838 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir1485160853/syzkaller.4PEQXG/233/bus" dev="sda1" ino=14593 res=1 audit: type=1804 audit(1666917712.760:1482): pid=17846 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir1485160853/syzkaller.4PEQXG/234/bus" dev="sda1" ino=14593 res=1 XFS (loop1): Invalid superblock magic number XFS (loop5): Invalid superblock magic number XFS (loop1): Invalid superblock magic number snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present XFS (loop0): Invalid superblock magic number snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present XFS (loop4): Invalid superblock magic number snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) snd_aloop snd_aloop.0: control 0:0:0:syz1:0 is already present XFS (loop0): Invalid superblock magic number xt_CT: You must specify a L4 protocol and not use inversions on it EXT4-fs (loop0): Unsupported blocksize for fs encryption xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it EXT4-fs (loop0): Unsupported blocksize for fs encryption