======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u8:2/40 is trying to acquire lock:
ffff888033438128 (&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:
ffff8880367760a0 (&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+0x75/0xe0 fs/hfs/dir.c:202
       lookup_open fs/namei.c:4489 [inline]
       open_last_lookups fs/namei.c:4589 [inline]
       path_openat+0x13b4/0x38a0 fs/namei.c:4833
       do_file_open+0x23e/0x4a0 fs/namei.c:4865
       do_sys_openat2+0x113/0x200 fs/open.c:1366
       do_sys_open fs/open.c:1372 [inline]
       __do_sys_open fs/open.c:1380 [inline]
       __se_sys_open fs/open.c:1376 [inline]
       __x64_sys_open+0x11e/0x150 fs/open.c:1376
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/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+0xf0/0x2e0 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:459
       write_inode fs/fs-writeback.c:1582 [inline]
       __writeback_single_inode+0x75d/0x11a0 fs/fs-writeback.c:1825
       writeback_sb_inodes+0x995/0x19d0 fs/fs-writeback.c:2054
       wb_writeback+0x456/0xb70 fs/fs-writeback.c:2239
       wb_do_writeback fs/fs-writeback.c:2386 [inline]
       wb_workfn+0x41a/0xf60 fs/fs-writeback.c:2426
       process_one_work kernel/workqueue.c:3276 [inline]
       process_scheduled_works+0xb6e/0x18c0 kernel/workqueue.c:3359
       worker_thread+0xa53/0xfc0 kernel/workqueue.c:3440
       kthread+0x388/0x470 kernel/kthread.c:436
       ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

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:2/40:
 #0: ffff88801f2cd138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3251 [inline]
 #0: ffff88801f2cd138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0xa52/0x18c0 kernel/workqueue.c:3359
 #1: ffffc90000b17c40 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3252 [inline]
 #1: ffffc90000b17c40 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa8d/0x18c0 kernel/workqueue.c:3359
 #2: ffff8880367760a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x300 fs/hfs/bfind.c:-1

stack backtrace:
CPU: 1 UID: 0 PID: 40 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: writeback wb_workfn (flush-7:7)
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+0xf0/0x2e0 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:459
 write_inode fs/fs-writeback.c:1582 [inline]
 __writeback_single_inode+0x75d/0x11a0 fs/fs-writeback.c:1825
 writeback_sb_inodes+0x995/0x19d0 fs/fs-writeback.c:2054
 wb_writeback+0x456/0xb70 fs/fs-writeback.c:2239
 wb_do_writeback fs/fs-writeback.c:2386 [inline]
 wb_workfn+0x41a/0xf60 fs/fs-writeback.c:2426
 process_one_work kernel/workqueue.c:3276 [inline]
 process_scheduled_works+0xb6e/0x18c0 kernel/workqueue.c:3359
 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3440
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </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:2/40
Modules linked in:
CPU: 1 UID: 0 PID: 40 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Workqueue: writeback wb_workfn (flush-7:7)
RIP: 0010:hfs_bnode_create+0x461/0x4f0 fs/hfs/bnode.c:520
Code: 67 8b 89 ee e8 f0 c8 82 fe e9 cf fc ff ff e8 26 e7 1f ff 4c 89 ef e8 3e 11 82 08 48 c7 c7 80 46 67 8b 89 ee e8 d0 c8 82 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:ffffc90000b16c60 EFLAGS: 00010246
RAX: 000000000000001f RBX: ffff888036776000 RCX: 7c554478301fb900
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101712491b R12: 0000000000000000
R13: ffff8880367760d0 R14: ffff88802d5f5400 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888126432000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffda9e68e40 CR3: 0000000040ce8000 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:459
 write_inode fs/fs-writeback.c:1582 [inline]
 __writeback_single_inode+0x75d/0x11a0 fs/fs-writeback.c:1825
 writeback_sb_inodes+0x995/0x19d0 fs/fs-writeback.c:2054
 wb_writeback+0x456/0xb70 fs/fs-writeback.c:2239
 wb_do_writeback fs/fs-writeback.c:2386 [inline]
 wb_workfn+0x41a/0xf60 fs/fs-writeback.c:2426
 process_one_work kernel/workqueue.c:3276 [inline]
 process_scheduled_works+0xb6e/0x18c0 kernel/workqueue.c:3359
 worker_thread+0xa53/0xfc0 kernel/workqueue.c:3440
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>