======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u8:0/12 is trying[ 589.716844][ T12] kworker/u8:0/12 is trying to acquire lock:
ffff888037152ca8 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xda/0x14c0 fs/hfs/extent.c:397
but task is already holding lock:
ffff88802998e0a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x2c0 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}:
lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
__mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
hfs_find_init+0x18e/0x2c0 fs/hfs/bfind.c:-1
hfs_ext_read_extent fs/hfs/extent.c:200 [inline]
hfs_extend_file+0x2f6/0x14c0 fs/hfs/extent.c:401
hfs_bmap_reserve+0x107/0x430 fs/hfs/btree.c:269
hfs_cat_create+0x1c5/0x730 fs/hfs/catalog.c:104
hfs_create+0x66/0xe0 fs/hfs/dir.c:202
lookup_open fs/namei.c:3796 [inline]
open_last_lookups fs/namei.c:3895 [inline]
path_openat+0x1500/0x3840 fs/namei.c:4131
do_filp_open+0x1fa/0x410 fs/namei.c:4161
do_sys_openat2+0x121/0x1c0 fs/open.c:1437
do_sys_open fs/open.c:1452 [inline]
__do_sys_openat fs/open.c:1468 [inline]
__se_sys_openat fs/open.c:1463 [inline]
__x64_sys_openat+0x138/0x170 fs/open.c:1463
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908
__lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
__mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
hfs_extend_file+0xda/0x14c0 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+0x161/0x1e0 fs/hfs/extent.c:144
hfs_write_inode+0xc6/0x870 fs/hfs/inode.c:440
write_inode fs/fs-writeback.c:1564 [inline]
__writeback_single_inode+0x6f4/0x1000 fs/fs-writeback.c:1784
writeback_sb_inodes+0x6b7/0xf60 fs/fs-writeback.c:2015
wb_writeback+0x43b/0xaf0 fs/fs-writeback.c:2195
wb_do_writeback fs/fs-writeback.c:2342 [inline]
wb_workfn+0x40e/0xf00 fs/fs-writeback.c:2382
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 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:0/12:
#0: ffff88814046a938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
#0: ffff88814046a938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3346
#1: ffffc90000117ba0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
#1: ffffc90000117ba0 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3346
#2: ffff88802998e0a0 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18e/0x2c0 fs/hfs/bfind.c:-1
stack backtrace:
CPU: 1 UID: 0 PID: 12 Comm: kworker/u8:0 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: writeback wb_workfn (flush-7:3)
Call Trace:
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043
check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908
__lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
__mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline]
mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547
hfs_extend_file+0xda/0x14c0 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+0x161/0x1e0 fs/hfs/extent.c:144
hfs_write_inode+0xc6/0x870 fs/hfs/inode.c:440
write_inode fs/fs-writeback.c:1564 [inline]
__writeback_single_inode+0x6f4/0x1000 fs/fs-writeback.c:1784
writeback_sb_inodes+0x6b7/0xf60 fs/fs-writeback.c:2015
wb_writeback+0x43b/0xaf0 fs/fs-writeback.c:2195
wb_do_writeback fs/fs-writeback.c:2342 [inline]
wb_workfn+0x40e/0xf00 fs/fs-writeback.c:2382
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
hfs: new node 0 already hashed?
------------[ cut here ]------------
WARNING: CPU: 0 PID: 12 at fs/hfs/bnode.c:520 hfs_bnode_create+0x461/0x4f0 fs/hfs/bnode.c:520
Modules linked in:
CPU: 0 UID: 0 PID: 12 Comm: kworker/u8:0 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: writeback wb_workfn (flush-7:3)
RIP: 0010:hfs_bnode_create+0x461/0x4f0 fs/hfs/bnode.c:520
Code: 01 8b 89 ee e8 c0 2e 93 fe e9 cf fc ff ff e8 16 f0 2a ff 4c 89 ef e8 2e f8 34 08 48 c7 c7 60 bf 01 8b 89 ee e8 a0 2e 93 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:ffffc90000116c00 EFLAGS: 00010246
RAX: 000000000000001f RBX: ffff88802998e000 RCX: 352ad1386cd43f00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000022d25 R12: 0000000000000000
R13: ffff88802998e0d0 R14: ffff88803d890c00 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888126bc6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055556cabf5c8 CR3: 0000000020ef8000 CR4: 00000000003526f0
Call Trace:
hfs_bmap_alloc+0x5bb/0x640 fs/hfs/btree.c:326
hfs_btree_inc_height+0xf6/0xac0 fs/hfs/brec.c:490
hfs_brec_insert+0x7c2/0xc60 fs/hfs/brec.c:148
__hfs_ext_write_extent+0x2a1/0x470 fs/hfs/extent.c:124
hfs_ext_write_extent+0x161/0x1e0 fs/hfs/extent.c:144
hfs_write_inode+0xc6/0x870 fs/hfs/inode.c:440
write_inode fs/fs-writeback.c:1564 [inline]
__writeback_single_inode+0x6f4/0x1000 fs/fs-writeback.c:1784
writeback_sb_inodes+0x6b7/0xf60 fs/fs-writeback.c:2015
wb_writeback+0x43b/0xaf0 fs/fs-writeback.c:2195
wb_do_writeback fs/fs-writeback.c:2342 [inline]
wb_workfn+0x40e/0xf00 fs/fs-writeback.c:2382
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245