====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ kworker/u8:9/1158 is trying to acquire lock: ffff888051f13460 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397 but task is already holding lock: ffff8880351600a8 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18d/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/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 hfs_find_init+0x18d/0x300 fs/hfs/bfind.c:-1 hfs_ext_read_extent fs/hfs/extent.c:200 [inline] hfs_extend_file+0x35f/0x1680 fs/hfs/extent.c:401 hfs_bmap_reserve+0x108/0x430 fs/hfs/btree.c:269 hfs_cat_create+0x221/0x810 fs/hfs/catalog.c:104 hfs_mkdir+0x79/0xe0 fs/hfs/dir.c:226 vfs_mkdir+0x406/0x620 fs/namei.c:5276 filename_mkdirat+0x285/0x510 fs/namei.c:5309 __do_sys_mkdir fs/namei.c:5336 [inline] __se_sys_mkdir+0x34/0x150 fs/namei.c:5333 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x174/0x580 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+0x1520/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397 hfs_bmap_reserve+0x108/0x430 fs/hfs/btree.c:269 __hfs_ext_write_extent+0x1fc/0x470 fs/hfs/extent.c:121 hfs_ext_write_extent+0x17e/0x210 fs/hfs/extent.c:144 hfs_write_inode+0x116/0x990 fs/hfs/inode.c:461 write_inode fs/fs-writeback.c:1607 [inline] __writeback_single_inode+0x6ac/0xf90 fs/fs-writeback.c:1850 writeback_sb_inodes+0x9de/0x1b00 fs/fs-writeback.c:2079 wb_writeback+0x41c/0xad0 fs/fs-writeback.c:2264 wb_do_writeback fs/fs-writeback.c:2432 [inline] wb_workfn+0x431/0x10f0 fs/fs-writeback.c:2477 process_one_work kernel/workqueue.c:3322 [inline] process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3486 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 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:9/1158: #0: ffff88801f6f7140 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline] #0: ffff88801f6f7140 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405 #1: ffffc900057dfc40 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3297 [inline] #1: ffffc900057dfc40 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0 kernel/workqueue.c:3405 #2: ffff8880351600a8 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18d/0x300 fs/hfs/bfind.c:-1 stack backtrace: CPU: 1 UID: 0 PID: 1158 Comm: kworker/u8:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026 Workqueue: writeback wb_workfn (flush-7:5) Call Trace: 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+0x1520/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/mutex.c:646 [inline] __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821 hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397 hfs_bmap_reserve+0x108/0x430 fs/hfs/btree.c:269 __hfs_ext_write_extent+0x1fc/0x470 fs/hfs/extent.c:121 hfs_ext_write_extent+0x17e/0x210 fs/hfs/extent.c:144 hfs_write_inode+0x116/0x990 fs/hfs/inode.c:461 write_inode fs/fs-writeback.c:1607 [inline] __writeback_single_inode+0x6ac/0xf90 fs/fs-writeback.c:1850 writeback_sb_inodes+0x9de/0x1b00 fs/fs-writeback.c:2079 wb_writeback+0x41c/0xad0 fs/fs-writeback.c:2264 wb_do_writeback fs/fs-writeback.c:2432 [inline] wb_workfn+0x431/0x10f0 fs/fs-writeback.c:2477 process_one_work kernel/workqueue.c:3322 [inline] process_scheduled_works+0xa8e/0x14e0 kernel/workqueue.c:3405 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3486 kthread+0x388/0x470 kernel/kthread.c:436 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 wlan0: Created IBSS using preconfigured BSSID 50:50:50:50:50:50 wlan0: Creating new IBSS network, BSSID 50:50:50:50:50:50