REISERFS warning (device loop5): jdm-13090 reiserfs_new_inode: ACLs aren't enabled in the fs, but vfs thinks they are! REISERFS warning (device loop5): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 4) not found (pos 2) REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 4.14.303-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/10927 is trying to acquire lock: (sb_writers#22){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] (sb_writers#22){.+.+}, 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#14){+.+.}: 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#22){.+.+}: 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#22 --> &type->i_mutex_dir_key#14 --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#14); lock(&sbi->lock); lock(sb_writers#22); *** DEADLOCK *** 1 lock held by syz-executor.5/10927: #0: (&sbi->lock){+.+.}, at: [] reiserfs_write_lock+0x75/0xf0 fs/reiserfs/lock.c:27 stack backtrace: CPU: 1 PID: 10927 Comm: syz-executor.5 Not tainted 4.14.303-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 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:0x7f675b81d0c9 RSP: 002b:00007f6759d8f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f675b93cf80 RCX: 00007f675b81d0c9 RDX: 0000000000000000 RSI: 0000000040087602 RDI: 0000000000000004 RBP: 00007f675b878ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffa029ce2f R14: 00007f6759d8f300 R15: 0000000000022000 UDF-fs: error (device loop3): udf_read_tagged: read failed, block=2016, location=2016 process 'syz-executor.5' launched './file0' with NULL argv: empty string added BTRFS: device fsid 395ef67a-297e-477c-816d-cd80a5b93e5d devid 1 transid 8 /dev/loop4 BTRFS error (device loop4): unsupported checksum algorithm 2 BTRFS error (device loop4): superblock checksum mismatch BTRFS error (device loop4): open_ctree failed audit: type=1800 audit(1674506496.516:57): pid=11022 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=14040 res=0 audit: type=1800 audit(1674506496.516:58): pid=11022 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="bus" dev="sda1" ino=14040 res=0 IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue netlink: 4 bytes leftover after parsing attributes in process `syz-executor.1'. IPVS: ftp: loaded support on port[0] = 21 befs: (md0): No write support. Marking filesystem read-only EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue befs: (md0): No write support. Marking filesystem read-only netlink: 4 bytes leftover after parsing attributes in process `syz-executor.1'. befs: (md0): No write support. Marking filesystem read-only befs: (md0): No write support. Marking filesystem read-only EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue netlink: 4 bytes leftover after parsing attributes in process `syz-executor.1'. EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue IPv6: ADDRCONF(NETDEV_UP): team_slave_0: link is not ready IPv6: ADDRCONF(NETDEV_CHANGE): team_slave_0: link becomes ready netlink: 4 bytes leftover after parsing attributes in process `syz-executor.1'. PM: Marking nosave pages: [mem 0x00000000-0x00000fff] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] PM: Marking nosave pages: [mem 0xbfffd000-0xffffffff] device lo entered promiscuous mode PM: Basic memory bitmaps created PM: Basic memory bitmaps freed Y4cRݘOC: renamed from lo EXT4-fs (loop1): Ignoring removed orlov option EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support! EXT4-fs (loop1): feature flags set on rev 0 fs, running e2fsck is recommended netlink: 36735 bytes leftover after parsing attributes in process `syz-executor.2'. hfs: get root inode failed A link change request failed with some changes committed already. Interface bridge0 may have been left with an inconsistent configuration, please check. ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root hfs: get root inode failed netlink: 36735 bytes leftover after parsing attributes in process `syz-executor.2'. A link change request failed with some changes committed already. Interface bridge0 may have been left with an inconsistent configuration, please check. hfs: get root inode failed ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root netlink: 36735 bytes leftover after parsing attributes in process `syz-executor.2'. A link change request failed with some changes committed already. Interface bridge0 may have been left with an inconsistent configuration, please check. device veth3 entered promiscuous mode hfs: get root inode failed IPv6: ADDRCONF(NETDEV_UP): veth3: link is not ready print_req_error: I/O error, dev loop0, sector 0 Buffer I/O error on dev loop0, logical block 0, async page read print_req_error: I/O error, dev loop0, sector 1 ISO 9660 Extensions: Microsoft Joliet Level 3 Buffer I/O error on dev loop0, logical block 1, async page read ISOFS: changing to secondary root print_req_error: I/O error, dev loop0, sector 4 Buffer I/O error on dev loop0, logical block 4, async page read print_req_error: I/O error, dev loop0, sector 5 Buffer I/O error on dev loop0, logical block 5, async page read print_req_error: I/O error, dev loop0, sector 6 Buffer I/O error on dev loop0, logical block 6, async page read print_req_error: I/O error, dev loop0, sector 7 Buffer I/O error on dev loop0, logical block 7, async page read netlink: 36735 bytes leftover after parsing attributes in process `syz-executor.2'. A link change request failed with some changes committed already. Interface bridge0 may have been left with an inconsistent configuration, please check. ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root device veth5 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth5: link is not ready device veth7 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth7: link is not ready device veth3 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth3: link is not ready audit: type=1800 audit(1674506502.117:59): pid=11563 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="loop3" ino=7 res=0 device veth9 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth9: link is not ready device veth5 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth5: link is not ready audit: type=1800 audit(1674506503.377:60): pid=11644 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="loop3" ino=7 res=0 device veth7 entered promiscuous mode IPv6: ADDRCONF(NETDEV_UP): veth7: link is not ready NILFS (nullb0): couldn't find nilfs on the device netlink: 20 bytes leftover after parsing attributes in process `syz-executor.4'. NILFS (nullb0): couldn't find nilfs on the device netlink: 20 bytes leftover after parsing attributes in process `syz-executor.4'. NILFS (nullb0): couldn't find nilfs on the device audit: type=1800 audit(1674506504.277:61): pid=11725 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="loop3" ino=7 res=0 NILFS (nullb0): couldn't find nilfs on the device netlink: 20 bytes leftover after parsing attributes in process `syz-executor.4'. audit: type=1800 audit(1674506504.717:62): pid=11799 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="bus" dev="loop3" ino=7 res=0 netlink: 20 bytes leftover after parsing attributes in process `syz-executor.4'. block nbd3: Attempted send on invalid socket print_req_error: I/O error, dev nbd3, sector 16 SQUASHFS error: Unable to read inode 0xa7 block nbd3: Attempted send on invalid socket print_req_error: I/O error, dev nbd3, sector 16 SQUASHFS error: Unable to read inode 0xa7