hfsplus: b-tree write err: -5, ino 3 ============================================ WARNING: possible recursive locking detected syzkaller #0 Not tainted -------------------------------------------- kworker/u4:3/766 is trying to acquire lock: ffff8880753840b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 but task is already holding lock: ffff8880753840b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 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:3/766: #0: ffff888142bc1938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1 #1: ffffc90003a0fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285 #2: ffff888023cf8108 (&hip->extents_lock){+.+.}-{3:3}, at: hfsplus_ext_write_extent+0x8d/0x220 fs/hfsplus/extents.c:149 #3: ffff8880753840b0 (&tree->tree_lock/1){+.+.}-{3:3}, at: hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 #4: ffff888028f90108 (&HFSPLUS_I(inode)->extents_lock){+.+.}-{3:3}, at: hfsplus_file_extend+0x1cd/0x1a50 fs/hfsplus/extents.c:455 stack backtrace: CPU: 0 PID: 766 Comm: kworker/u4:3 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 __lock_acquire+0x1236/0x7d10 kernel/locking/lockdep.c:-1 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1e3/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 hfsplus_find_init+0x150/0x1c0 fs/hfsplus/bfind.c:28 hfsplus_ext_read_extent fs/hfsplus/extents.c:216 [inline] hfsplus_file_extend+0x46a/0x1a50 fs/hfsplus/extents.c:459 hfsplus_bmap_reserve+0x11e/0x4f0 fs/hfsplus/btree.c:357 __hfsplus_ext_write_extent+0x28d/0x5b0 fs/hfsplus/extents.c:104 hfsplus_ext_write_extent_locked fs/hfsplus/extents.c:139 [inline] hfsplus_ext_write_extent+0x194/0x220 fs/hfsplus/extents.c:150 hfsplus_write_inode+0x1e/0x5b0 fs/hfsplus/super.c:167 write_inode fs/fs-writeback.c:1505 [inline] __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715 writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940 wb_writeback+0x45d/0xbe0 fs/fs-writeback.c:2114 wb_do_writeback fs/fs-writeback.c:2257 [inline] wb_workfn+0x43a/0xf20 fs/fs-writeback.c:2298 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287