BTRFS: device fsid d552757d-9c39-40e3-95f0-16d819589928 devid 1 transid 8 /dev/loop3 BTRFS error (device loop3): unsupported checksum algorithm 2 REISERFS (device loop0): Using r5 hash to sort names BTRFS error (device loop3): superblock checksum mismatch ====================================================== WARNING: possible circular locking dependency detected 4.14.302-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/12272 is trying to acquire lock: (sb_writers#16){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] (sb_writers#16){.+.+}, at: [] mnt_want_write_file+0xfd/0x3b0 fs/namespace.c:497 but task is already holding lock: (&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){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 reiserfs_lookup+0x130/0x400 fs/reiserfs/namei.c:363 lookup_real fs/namei.c:1555 [inline] __lookup_hash fs/namei.c:1575 [inline] __lookup_hash+0x1bb/0x270 fs/namei.c:1563 lookup_one_len+0x279/0x3a0 fs/namei.c:2539 reiserfs_lookup_privroot+0x92/0x270 fs/reiserfs/xattr.c:970 reiserfs_fill_super+0x1d12/0x2990 fs/reiserfs/super.c:2187 mount_bdev+0x2b3/0x360 fs/super.c:1134 mount_fs+0x92/0x2a0 fs/super.c:1237 vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046 vfs_kern_mount fs/namespace.c:1036 [inline] do_new_mount fs/namespace.c:2572 [inline] do_mount+0xe65/0x2a30 fs/namespace.c:2905 SYSC_mount fs/namespace.c:3121 [inline] SyS_mount+0xa8/0x120 fs/namespace.c:3098 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #1 (&type->i_mutex_dir_key#12){++++}: down_write+0x34/0x90 kernel/locking/rwsem.c:54 inode_lock include/linux/fs.h:719 [inline] do_last fs/namei.c:3331 [inline] path_openat+0xde2/0x2970 fs/namei.c:3571 do_filp_open+0x179/0x3c0 fs/namei.c:3605 do_sys_open+0x296/0x410 fs/open.c:1081 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #0 (sb_writers#16){.+.+}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 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+0x64/0x260 fs/super.c:1342 sb_start_write include/linux/fs.h:1551 [inline] mnt_want_write_file+0xfd/0x3b0 fs/namespace.c:497 reiserfs_ioctl+0x18e/0x8b0 fs/reiserfs/ioctl.c:110 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 other info that might help us debug this: Chain exists of: sb_writers#16 --> &type->i_mutex_dir_key#12 --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#12); lock(&sbi->lock); lock(sb_writers#16); *** DEADLOCK *** 1 lock held by syz-executor.0/12272: #0: (&sbi->lock){+.+.}, at: [] reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 stack backtrace: CPU: 0 PID: 12272 Comm: syz-executor.0 Not tainted 4.14.302-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 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+0x64/0x260 fs/super.c:1342 sb_start_write include/linux/fs.h:1551 [inline] mnt_want_write_file+0xfd/0x3b0 fs/namespace.c:497 reiserfs_ioctl+0x18e/0x8b0 fs/reiserfs/ioctl.c:110 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:500 [inline] do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684 SYSC_ioctl fs/ioctl.c:701 [inline] SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 RIP: 0033:0x7f385d0820c9 RSP: 002b:00007f385b5f4168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f385d1a1f80 RCX: 00007f385d0820c9 RDX: 0000000000000000 RSI: 0000000040087602 RDI: 0000000000000003 RBP: 00007f385d0ddae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff03fd32ff R14: 00007f385b5f4300 R15: 0000000000022000 BTRFS error (device loop3): open_ctree failed netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. device bridge_slave_1 left promiscuous mode IPVS: ftp: loaded support on port[0] = 21 bridge0: port 2(bridge_slave_1) entered disabled state bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. IPVS: ftp: loaded support on port[0] = 21 bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode netlink: 12 bytes leftover after parsing attributes in process `syz-executor.5'. device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 left promiscuous mode bridge0: port 2(bridge_slave_1) entered disabled state bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode netlink: 12 bytes leftover after parsing attributes in process `syz-executor.5'. device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state netlink: 12 bytes leftover after parsing attributes in process `syz-executor.0'. bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state netlink: 12 bytes leftover after parsing attributes in process `syz-executor.5'. bridge1: port 1(bridge_slave_1) entered blocking state bridge1: port 1(bridge_slave_1) entered disabled state device bridge_slave_1 entered promiscuous mode device bridge_slave_1 left promiscuous mode bridge1: port 1(bridge_slave_1) entered disabled state xt_recent: hitcount (1280) is larger than allowed maximum (255) kernel profiling enabled (shift: 0) EXT4-fs (loop0): ext4_check_descriptors: Checksum for group 0 failed (57538!=33349) EXT4-fs (loop0): Unsupported blocksize for fs encryption Cannot find set identified by id 0 to match audit: type=1800 audit(1673356377.519:7): pid=12965 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14266 res=0 audit: type=1800 audit(1673356377.519:8): pid=12967 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="sda1" ino=14267 res=0 Cannot find set identified by id 0 to match Cannot find set identified by id 0 to match EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue audit: type=1800 audit(1673356378.329:9): pid=13005 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="bus" dev="loop1" ino=18 res=0 Cannot find set identified by id 0 to match audit: type=1800 audit(1673356378.379:10): pid=13027 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14281 res=0 EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue audit: type=1800 audit(1673356378.749:11): pid=13025 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="loop2" ino=18 res=0 audit: type=1800 audit(1673356378.789:12): pid=13056 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="sda1" ino=14265 res=0 EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue audit: type=1800 audit(1673356378.879:13): pid=13070 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="sda1" ino=14287 res=0 audit: type=1800 audit(1673356378.939:14): pid=13050 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.1" name="bus" dev="loop1" ino=18 res=0 audit: type=1800 audit(1673356379.309:15): pid=13082 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="bus" dev="sda1" ino=14279 res=0 audit: type=1800 audit(1673356379.759:16): pid=13107 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="sda1" ino=14233 res=0