======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u8:11/3984 is trying to acquire l[  154.807898][ T3984] kworker/u8:11/3984 is trying to acquire lock:
ffff888033a296e8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xf2/0x15e0 fs/hfs/extent.c:397

but task is already holding lock:
ffff888033d780a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300 fs/hfs/bfind.c:-1

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&tree->tree_lock/1){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       hfs_find_init+0x18e/0x300 fs/hfs/bfind.c:-1
       hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
       hfs_extend_file+0x35c/0x15e0 fs/hfs/extent.c:401
       hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
       hfs_cat_create+0x20f/0x800 fs/hfs/catalog.c:104
       hfs_create+0x66/0xe0 fs/hfs/dir.c:202
       vfs_create+0x5ff/0x6d0 fs/namei.c:4141
       do_mknodat+0x3f5/0x630 fs/namei.c:5048
       __do_sys_mknod fs/namei.c:5085 [inline]
       __se_sys_mknod fs/namei.c:5083 [inline]
       __x64_sys_mknod+0x8c/0xa0 fs/namei.c:5083
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xe2/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
       __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
       mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
       hfs_extend_file+0xf2/0x15e0 fs/hfs/extent.c:397
       hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
       __hfs_ext_write_extent+0x1fa/0x470 fs/hfs/extent.c:121
       hfs_ext_write_extent+0x17e/0x210 fs/hfs/extent.c:144
       hfs_write_inode+0x117/0x960 fs/hfs/inode.c:441
       write_inode fs/fs-writeback.c:1582 [inline]
       __writeback_single_inode+0x7e4/0x1230 fs/fs-writeback.c:1802
       writeback_sb_inodes+0x92e/0x1910 fs/fs-writeback.c:2030
       wb_writeback+0x445/0xad0 fs/fs-writeback.c:2216
       wb_do_writeback fs/fs-writeback.c:2363 [inline]
       wb_workfn+0x3fd/0xf00 fs/fs-writeback.c:2403
       process_one_work kernel/workqueue.c:3257 [inline]
       process_scheduled_works+0xaec/0x17a0 kernel/workqueue.c:3340
       worker_thread+0xda6/0x1360 kernel/workqueue.c:3421
       kthread+0x726/0x8b0 kernel/kthread.c:463
       ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&tree->tree_lock/1);
                               lock(&HFS_I(tree->inode)->extents_lock);
                               lock(&tree->tree_lock/1);
  lock(&HFS_I(tree->inode)->extents_lock);

 *** DEADLOCK ***

3 locks held by kworker/u8:11/3984:
 #0: ffff8881416c9138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3232 [inline]
 #0: ffff8881416c9138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x9d4/0x17a0 kernel/workqueue.c:3340
 #1: ffffc9000eeffbc0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3233 [inline]
 #1: ffffc9000eeffbc0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa0f/0x17a0 kernel/workqueue.c:3340
 #2: ffff888033d780a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300 fs/hfs/bfind.c:-1

stack backtrace:
CPU: 1 UID: 0 PID: 3984 Comm: kworker/u8:11 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: writeback wb_workfn (flush-7:6)
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
 __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline]
 mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552
 hfs_extend_file+0xf2/0x15e0 fs/hfs/extent.c:397
 hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
 __hfs_ext_write_extent+0x1fa/0x470 fs/hfs/extent.c:121
 hfs_ext_write_extent+0x17e/0x210 fs/hfs/extent.c:144
 hfs_write_inode+0x117/0x960 fs/hfs/inode.c:441
 write_inode fs/fs-writeback.c:1582 [inline]
 __writeback_single_inode+0x7e4/0x1230 fs/fs-writeback.c:1802
 writeback_sb_inodes+0x92e/0x1910 fs/fs-writeback.c:2030
 wb_writeback+0x445/0xad0 fs/fs-writeback.c:2216
 wb_do_writeback fs/fs-writeback.c:2363 [inline]
 wb_workfn+0x3fd/0xf00 fs/fs-writeback.c:2403
 process_one_work kernel/workqueue.c:3257 [inline]
 process_scheduled_works+0xaec/0x17a0 kernel/workqueue.c:3340
 worker_thread+0xda6/0x1360 kernel/workqueue.c:3421
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
hfs: new node 0 already hashed?
------------[ cut here ]------------
1
WARNING: fs/hfs/bnode.c:520 at hfs_bnode_create+0x461/0x4f0 fs/hfs/bnode.c:520, CPU#1: kworker/u8:11/3984
Modules linked in:
CPU: 1 UID: 0 PID: 3984 Comm: kworker/u8:11 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: writeback wb_workfn (flush-7:6)
RIP: 0010:hfs_bnode_create+0x461/0x4f0 fs/hfs/bnode.c:520
Code: 46 8b 89 ee e8 d0 17 88 fe e9 cf fc ff ff e8 16 f5 23 ff 4c 89 ef e8 5e 95 70 08 48 c7 c7 e0 f3 46 8b 89 ee e8 b0 17 88 fe 90 <0f> 0b 90 eb b0 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c d6 fb ff ff
RSP: 0018:ffffc9000eefec20 EFLAGS: 00010246
RAX: 000000000000001f RBX: ffff888033d78000 RCX: c7a0eab9e980fa00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52001ddfd35 R12: 0000000000000000
R13: ffff888033d780d0 R14: ffff88803a399200 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8881266c9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007feaabe3d000 CR3: 0000000034652000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 hfs_bmap_alloc+0x5c1/0x650 fs/hfs/btree.c:326
 hfs_btree_inc_height+0x100/0xad0 fs/hfs/brec.c:490
 hfs_brec_insert+0x7ef/0xc90 fs/hfs/brec.c:148
 __hfs_ext_write_extent+0x2a1/0x470 fs/hfs/extent.c:124
 hfs_ext_write_extent+0x17e/0x210 fs/hfs/extent.c:144
 hfs_write_inode+0x117/0x960 fs/hfs/inode.c:441
 write_inode fs/fs-writeback.c:1582 [inline]
 __writeback_single_inode+0x7e4/0x1230 fs/fs-writeback.c:1802
 writeback_sb_inodes+0x92e/0x1910 fs/fs-writeback.c:2030
 wb_writeback+0x445/0xad0 fs/fs-writeback.c:2216
 wb_do_writeback fs/fs-writeback.c:2363 [inline]
 wb_workfn+0x3fd/0xf00 fs/fs-writeback.c:2403
 process_one_work kernel/workqueue.c:3257 [inline]
 process_scheduled_works+0xaec/0x17a0 kernel/workqueue.c:3340
 worker_thread+0xda6/0x1360 kernel/workqueue.c:3421
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>