hfsplus: b-tree write err: -5, ino 8 ============================================ WARNING: possible recursive locking detected 6.6.0-rc7-syzkaller-g8de1e7afcc1c #0 Not tainted -------------------------------------------- kworker/u4:0/11 is trying to acquire lock: ffff0000d74c00b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc but task is already holding lock: ffff0000d74c00b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&tree->tree_lock/1); lock(&tree->tree_lock/1); *** DEADLOCK *** May be due to missing lock nesting notation 5 locks held by kworker/u4:0/11: #0: ffff0000c1c0e138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x560/0x1204 kernel/workqueue.c:2603 #1: ffff800092d67c20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x5a0/0x1204 kernel/workqueue.c:2605 #2: ffff0000d55ea988 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x8c/0x1d8 fs/hfsplus/extents.c:149 #3: ffff0000d74c00b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x144/0x1bc #4: ffff0000d55e8108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1d0/0x1544 fs/hfsplus/extents.c:457 stack backtrace: CPU: 1 PID: 11 Comm: kworker/u4:0 Not tainted 6.6.0-rc7-syzkaller-g8de1e7afcc1c #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 Workqueue: writeback wb_workfn (flush-7:0) Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:233 show_stack+0x2c/0x44 arch/arm64/kernel/stacktrace.c:240 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 dump_stack+0x1c/0x28 lib/dump_stack.c:113 print_deadlock_bug+0x4e4/0x660 kernel/locking/lockdep.c:3012 check_deadlock kernel/locking/lockdep.c:3062 [inline] validate_chain kernel/locking/lockdep.c:3855 [inline] __lock_acquire+0x5fd0/0x75e8 kernel/locking/lockdep.c:5136 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5753 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799 hfsplus_find_init+0x144/0x1bc hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline] hfsplus_file_extend+0x370/0x1544 fs/hfsplus/extents.c:461 hfsplus_bmap_reserve+0xec/0x474 fs/hfsplus/btree.c:358 __hfsplus_ext_write_extent+0x1e8/0x4ac fs/hfsplus/extents.c:104 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline] hfsplus_ext_write_extent+0x158/0x1d8 fs/hfsplus/extents.c:150 hfsplus_write_inode+0x34/0x4dc fs/hfsplus/super.c:154 write_inode fs/fs-writeback.c:1456 [inline] __writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1673 writeback_sb_inodes+0x718/0x1010 fs/fs-writeback.c:1899 wb_writeback+0x3f4/0xfc0 fs/fs-writeback.c:2075 wb_do_writeback fs/fs-writeback.c:2222 [inline] wb_workfn+0x37c/0xf9c fs/fs-writeback.c:2262 process_one_work+0x694/0x1204 kernel/workqueue.c:2630 process_scheduled_works kernel/workqueue.c:2703 [inline] worker_thread+0x938/0xef4 kernel/workqueue.c:2784 kthread+0x288/0x310 kernel/kthread.c:388 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857