audit: type=1804 audit(1676098913.379:8): pid=9580 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir3063466221/syzkaller.PhpBc3/2/file0" dev="sda1" ino=13921 res=1 ============================================ WARNING: possible recursive locking detected 4.14.305-syzkaller #0 Not tainted -------------------------------------------- syz-executor.1/9591 is trying to acquire lock: (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: [] hfsplus_get_block+0x1f9/0x820 fs/hfsplus/extents.c:260 but task is already holding lock: (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: [] hfsplus_file_extend+0x188/0xef0 fs/hfsplus/extents.c:452 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&HFSPLUS_I(inode)->extents_lock); lock(&HFSPLUS_I(inode)->extents_lock); *** DEADLOCK *** May be due to missing lock nesting notation 5 locks held by syz-executor.1/9591: #0: (&type->s_umount_key#54/1){+.+.}, at: [] alloc_super fs/super.c:251 [inline] #0: (&type->s_umount_key#54/1){+.+.}, at: [] sget_userns+0x556/0xc10 fs/super.c:516 #1: (&sbi->vh_mutex){+.+.}, at: [] hfsplus_fill_super+0x1314/0x1850 fs/hfsplus/super.c:553 #2: (&tree->tree_lock){+.+.}, at: [] hfsplus_find_init+0x1a8/0x220 fs/hfsplus/bfind.c:30 #3: (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: [] hfsplus_file_extend+0x188/0xef0 fs/hfsplus/extents.c:452 #4: (&sbi->alloc_mutex){+.+.}, at: [] hfsplus_block_allocate+0xd2/0x910 fs/hfsplus/bitmap.c:35 stack backtrace: CPU: 1 PID: 9591 Comm: syz-executor.1 Not tainted 4.14.305-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_deadlock_bug kernel/locking/lockdep.c:1800 [inline] check_deadlock kernel/locking/lockdep.c:1847 [inline] validate_chain kernel/locking/lockdep.c:2448 [inline] __lock_acquire.cold+0x180/0x97c kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 hfsplus_get_block+0x1f9/0x820 fs/hfsplus/extents.c:260 block_read_full_page+0x25e/0x8d0 fs/buffer.c:2316 do_read_cache_page+0x38e/0xc10 mm/filemap.c:2713 read_mapping_page include/linux/pagemap.h:398 [inline] hfsplus_block_allocate+0x189/0x910 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x421/0xef0 fs/hfsplus/extents.c:463 hfsplus_bmap_reserve+0x26e/0x410 fs/hfsplus/btree.c:357 hfsplus_create_cat+0x1af/0x10d0 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x1386/0x1850 fs/hfsplus/super.c:560 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 RIP: 0033:0x7f29eeb7762a RSP: 002b:00007f29ed0e7f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 000000000000061b RCX: 00007f29eeb7762a RDX: 0000000020000600 RSI: 00000000200001c0 RDI: 00007f29ed0e7fe0 RBP: 00007f29ed0e8020 R08: 00007f29ed0e8020 R09: 0000000001a00010 R10: 0000000001a00010 R11: 0000000000000202 R12: 0000000020000600 R13: 00000000200001c0 R14: 00007f29ed0e7fe0 R15: 0000000020000140 audit: type=1800 audit(1676098913.989:9): pid=9594 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="file2" dev="sda1" ino=13919 res=0 L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. audit: type=1800 audit(1676098915.269:10): pid=9604 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="sda1" ino=13922 res=0 audit: type=1804 audit(1676098915.279:11): pid=9604 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir3063466221/syzkaller.PhpBc3/3/file0" dev="sda1" ino=13922 res=1 audit: type=1800 audit(1676098915.579:12): pid=9614 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="file2" dev="sda1" ino=13912 res=0 JFS: discard option not supported on device JFS: discard option not supported on device print_req_error: I/O error, dev loop1, sector 0 audit: type=1800 audit(1676098916.759:13): pid=9676 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.3" name="file2" dev="sda1" ino=13910 res=0 JFS: discard option not supported on device print_req_error: I/O error, dev loop1, sector 0 JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'. F2FS-fs (loop1): Mismatch start address, segment0(512) cp_blkaddr(605) F2FS-fs (loop1): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop1): invalid crc value F2FS-fs (loop1): Found nat_bits in checkpoint F2FS-fs (loop1): Mounted with checkpoint version = 753bd00b audit: type=1804 audit(1676098919.889:14): pid=9880 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir782315382/syzkaller.yYIppp/18/bus/bus" dev="loop1" ino=4 res=1 attempt to access beyond end of device loop1: rw=2049, want=77896, limit=63271 attempt to access beyond end of device loop1: rw=2049, want=77904, limit=63271 netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'. EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue audit: type=1804 audit(1676098920.320:15): pid=9897 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/19/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs error (device loop5): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop5): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 1 with error 28 audit: type=1804 audit(1676098920.320:16): pid=9897 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/19/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): This should not happen!! Data will be lost EXT4-fs (loop5): Total free blocks count 0 EXT4-fs (loop5): Free/Dirty block details EXT4-fs (loop5): free_blocks=2415919104 audit: type=1804 audit(1676098920.410:17): pid=9927 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/19/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): dirty_blocks=16 EXT4-fs (loop5): Block reservation details EXT4-fs (loop5): i_reserved_data_blocks=1 audit: type=1804 audit(1676098920.410:18): pid=9927 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/19/file0/bus" dev="loop5" ino=18 res=1 syz-executor.5 (9897) used greatest stack depth: 25176 bytes left F2FS-fs (loop1): Mismatch start address, segment0(512) cp_blkaddr(605) F2FS-fs (loop1): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop1): invalid crc value F2FS-fs (loop1): Found nat_bits in checkpoint F2FS-fs (loop1): Mounted with checkpoint version = 753bd00b attempt to access beyond end of device audit: type=1804 audit(1676098920.650:19): pid=9938 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir782315382/syzkaller.yYIppp/19/bus/bus" dev="loop1" ino=4 res=1 loop1: rw=2049, want=77952, limit=63271 attempt to access beyond end of device loop1: rw=2049, want=77960, limit=63271 netlink: 4 bytes leftover after parsing attributes in process `syz-executor.4'. EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue audit: type=1804 audit(1676098921.730:20): pid=9944 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/20/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs error (device loop5): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters EXT4-fs (loop5): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 1 with error 28 audit: type=1804 audit(1676098921.730:21): pid=9944 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/20/file0/bus" dev="loop5" ino=18 res=1 audit: type=1804 audit(1676098921.810:22): pid=9999 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/20/file0/bus" dev="loop5" ino=18 res=1 audit: type=1804 audit(1676098921.810:23): pid=9999 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/20/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): This should not happen!! Data will be lost EXT4-fs (loop5): Total free blocks count 0 audit: type=1804 audit(1676098921.880:24): pid=10002 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir782315382/syzkaller.yYIppp/20/bus/bus" dev="loop1" ino=4 res=1 attempt to access beyond end of device EXT4-fs (loop5): Free/Dirty block details loop1: rw=2049, want=77952, limit=63271 attempt to access beyond end of device loop1: rw=2049, want=77960, limit=63271 EXT4-fs (loop5): free_blocks=2415919104 EXT4-fs (loop5): dirty_blocks=16 EXT4-fs (loop5): Block reservation details EXT4-fs (loop5): i_reserved_data_blocks=1 audit: type=1804 audit(1676098923.370:25): pid=10062 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir782315382/syzkaller.yYIppp/21/bus/bus" dev="loop1" ino=4 res=1 attempt to access beyond end of device loop1: rw=2049, want=78024, limit=63271 attempt to access beyond end of device loop1: rw=2049, want=78032, limit=63271 EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue audit: type=1804 audit(1676098923.450:26): pid=10015 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/21/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs error (device loop5): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 25 vs 150994969 free clusters audit: type=1804 audit(1676098923.450:27): pid=10015 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/21/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 1 with error 28 audit: type=1804 audit(1676098923.520:28): pid=10069 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/21/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): This should not happen!! Data will be lost EXT4-fs (loop5): Total free blocks count 0 EXT4-fs (loop5): Free/Dirty block details EXT4-fs (loop5): free_blocks=2415919104 EXT4-fs (loop5): dirty_blocks=16 audit: type=1804 audit(1676098923.520:29): pid=10069 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir2933105985/syzkaller.qsgxwn/21/file0/bus" dev="loop5" ino=18 res=1 EXT4-fs (loop5): Block reservation details EXT4-fs (loop5): i_reserved_data_blocks=1 syz-executor.5 (10015) used greatest stack depth: 25064 bytes left sch_tbf: burst 0 is lower than device syz_tun mtu (1514) ! TCP: request_sock_TCPv6: Possible SYN flooding on port 20002. Sending cookies. Check SNMP counters. syz-executor.0 (10114) used greatest stack depth: 25040 bytes left