REISERFS (device loop5): Using r5 hash to sort names ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/1391 is trying to acquire lock: 000000005f91add5 (sb_writers#21){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] 000000005f91add5 (sb_writers#21){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 but task is already holding lock: 000000001d8caaaa (&sbi->lock){+.+.}, at: reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sbi->lock){+.+.}: reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x171/0x490 fs/reiserfs/namei.c:363 __lookup_hash+0x117/0x180 fs/namei.c:1547 filename_create+0x186/0x490 fs/namei.c:3639 user_path_create fs/namei.c:3696 [inline] do_mkdirat+0xa0/0x2d0 fs/namei.c:3834 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&type->i_mutex_dir_key#13/1){+.+.}: inode_lock_nested include/linux/fs.h:783 [inline] filename_create+0x15a/0x490 fs/namei.c:3638 user_path_create fs/namei.c:3696 [inline] do_mkdirat+0xa0/0x2d0 fs/namei.c:3834 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (sb_writers#21){.+.+}: percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x6e/0x2a0 fs/super.c:1366 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 other info that might help us debug this: Chain exists of: sb_writers#21 --> &type->i_mutex_dir_key#13/1 --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#13/1); lock(&sbi->lock); lock(sb_writers#21); *** DEADLOCK *** 1 lock held by syz-executor.5/1391: #0: 000000001d8caaaa (&sbi->lock){+.+.}, at: reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 stack backtrace: CPU: 1 PID: 1391 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/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 percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x6e/0x2a0 fs/super.c:1366 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 RIP: 0033:0x7f8c595c20c9 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:00007f8c57b34168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f8c596e1f80 RCX: 00007f8c595c20c9 RDX: 0000000000000000 RSI: 0000000040087602 RDI: 0000000000000003 RBP: 00007f8c5961dae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc16fe629f R14: 00007f8c57b34300 R15: 0000000000022000 REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 1822, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 1822, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 1822, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) gfs2: fsid=_proc_thread-self_attr_exec: Trying to join cluster "lock_nolock", "_proc_thread-self_attr_exec" gfs2: fsid=_proc_thread-self_attr_exec: Now mounting FS... gfs2: fsid=_proc_thread-self_attr_exec.0: journal 0 mapped with 3 extents gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0, already locked for use gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Looking at journal... REISERFS (device loop5): Using r5 hash to sort names gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Done gfs2: fsid=_proc_thread-self_attr_exec.0: first mount done, others may mount netlink: 'syz-executor.5': attribute type 4 has an invalid length. ********************************************************** IPv6: ADDRCONF(NETDEV_CHANGE): lo: link becomes ready ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** ** ** device veth3 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth3: link is not ready ** trace_printk() being used. Allocating extra memory. ** ** ** ** This means that this is a DEBUG kernel and it is ** ** unsafe for production use. ** ** ** ** If you see this message and you are not debugging ** ** the kernel, report this immediately to your vendor! ** ** ** ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE ** netlink: 'syz-executor.5': attribute type 4 has an invalid length. ********************************************************** gfs2: fsid=_proc_thread-self_attr_exec: Trying to join cluster "lock_nolock", "_proc_thread-self_attr_exec" gfs2: fsid=_proc_thread-self_attr_exec: Now mounting FS... gfs2: fsid=_proc_thread-self_attr_exec.0: journal 0 mapped with 3 extents gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0, already locked for use gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Looking at journal... gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Done gfs2: fsid=_proc_thread-self_attr_exec.0: first mount done, others may mount device veth5 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth5: link is not ready device veth9 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth9: link is not ready netlink: 'syz-executor.5': attribute type 4 has an invalid length. netlink: 'syz-executor.5': attribute type 4 has an invalid length. device veth11 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth11: link is not ready device veth7 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth7: link is not ready gfs2: fsid=_proc_thread-self_attr_exec: Trying to join cluster "lock_nolock", "_proc_thread-self_attr_exec" gfs2: fsid=_proc_thread-self_attr_exec: Now mounting FS... gfs2: fsid=_proc_thread-self_attr_exec.0: journal 0 mapped with 3 extents device veth11 entered promiscuous mode gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0, already locked for use gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Looking at journal... IPv6: ADDRCONF(NETDEV_UP): veth11: link is not ready gfs2: fsid=_proc_thread-self_attr_exec.0: jid=0: Done gfs2: fsid=_proc_thread-self_attr_exec.0: first mount done, others may mount device veth9 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth9: link is not ready device veth13 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth13: link is not ready device veth9 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth9: link is not ready device veth13 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth13: link is not ready device veth15 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth15: link is not ready device veth11 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth11: link is not ready device veth11 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth11: link is not ready