IPVS: sync thread started: state = BACKUP, mcast_ifn = vxcan1, syncid = 4, id = 0 hfsplus: invalid attributes max_key_len 0 hfsplus: failed to load attributes file ============================================ WARNING: possible recursive locking detected 4.14.305-syzkaller #0 Not tainted -------------------------------------------- syz-executor.0/10539 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.0/10539: #0: (&type->s_umount_key#60/1){+.+.}, at: [] alloc_super fs/super.c:251 [inline] #0: (&type->s_umount_key#60/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#2){+.+.}, 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: 0 PID: 10539 Comm: syz-executor.0 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:0x7fb55843862a RSP: 002b:00007fb5569a8f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 000000000000061b RCX: 00007fb55843862a RDX: 0000000020000600 RSI: 00000000200001c0 RDI: 00007fb5569a8fe0 RBP: 00007fb5569a9020 R08: 00007fb5569a9020 R09: 0000000001a00010 R10: 0000000001a00010 R11: 0000000000000202 R12: 0000000020000600 R13: 00000000200001c0 R14: 00007fb5569a8fe0 R15: 0000000020000140 EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue print_req_error: I/O error, dev loop3, sector 0 hfsplus: invalid attributes max_key_len 0 hfsplus: failed to load attributes file print_req_error: I/O error, dev loop3, sector 0 EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 hfsplus: invalid attributes max_key_len 0 hfsplus: failed to load attributes file print_req_error: I/O error, dev loop3, sector 0 hfsplus: invalid attributes max_key_len 0 FAT-fs (loop5): error, invalid access to FAT (entry 0x0fffff00) hfsplus: failed to load attributes file FAT-fs (loop5): Filesystem has been set read-only EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue FAT-fs (loop5): error, invalid access to FAT (entry 0x0fffff00) FAT-fs (loop5): Filesystem has been set read-only netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. FAT-fs (loop5): error, invalid access to FAT (entry 0x0fffff00) netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. FAT-fs (loop5): Filesystem has been set read-only netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. print_req_error: I/O error, dev loop5, sector 2 netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. Buffer I/O error on dev loop5, logical block 2, async page read netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. print_req_error: I/O error, dev loop5, sector 3 netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. Buffer I/O error on dev loop5, logical block 3, async page read netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 64 bytes leftover after parsing attributes in process `syz-executor.0'. print_req_error: I/O error, dev loop5, sector 4 Buffer I/O error on dev loop5, logical block 4, async page read print_req_error: I/O error, dev loop5, sector 5 Buffer I/O error on dev loop5, logical block 5, async page read print_req_error: I/O error, dev loop5, sector 6 Buffer I/O error on dev loop5, logical block 6, async page read print_req_error: I/O error, dev loop5, sector 7 Buffer I/O error on dev loop5, logical block 7, async page read FAT-fs (loop5): error, invalid access to FAT (entry 0x0fffff00) EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue FAT-fs (loop5): Filesystem has been set read-only REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) EXT4-fs (loop0): feature flags set on rev 0 fs, running e2fsck is recommended EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem EXT4-fs (loop0): warning: mounting unchecked fs, running e2fsck is recommended REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs warning (device loop0): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT4-fs (loop0): mounted filesystem without journal. Opts: max_dir_size_kb=0x00000000000001c1,,errors=continue EXT4-fs error (device loop0): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 159 vs 2 free clusters nla_parse: 3961 callbacks suppressed netlink: 4 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'. REISERFS (device loop2): found reiserfs format "3.6" with non-standard journal REISERFS (device loop2): using ordered data mode EXT4-fs (loop0): feature flags set on rev 0 fs, running e2fsck is recommended reiserfs: using flush barriers EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem