syzbot


possible deadlock in __btrfs_release_delayed_node (5)

Status: upstream: reported on 2025/12/19 11:02
Subsystems: btrfs
[Documentation on labels]
Reported-by: syzbot+c1c6edb02bea1da754d8@syzkaller.appspotmail.com
Fix commit: btrfs: release path before iget_failed() in btrfs_read_locked_inode()
Patched on: [ci-upstream-linux-next-kasan-gce-root ci-upstream-rust-kasan-gce], missing on: [ci-qemu-gce-upstream-auto ci-qemu-native-arm64-kvm ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-qemu2-riscv64 ci-snapshot-upstream-root ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-badwrites-root ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce-386-root ci-upstream-kmsan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb]
First crash: 23d, last: 23d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [btrfs?] possible deadlock in __btrfs_release_delayed_node (5) 0 (1) 2025/12/19 11:02
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in __btrfs_release_delayed_node btrfs 4 1 1145d 1145d 22/29 fixed on 2023/02/24 13:50
upstream possible deadlock in __btrfs_release_delayed_node (4) btrfs 4 22 292d 406d 0/29 auto-obsoleted due to no activity on 2025/06/07 10:53
upstream possible deadlock in __btrfs_release_delayed_node (3) btrfs 4 syz 2 866d 862d 25/29 fixed on 2023/12/21 03:45
upstream possible deadlock in __btrfs_release_delayed_node (2) btrfs 4 1 1028d 1024d 0/29 auto-obsoleted due to no activity on 2023/07/13 23:06

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
btrfs-cleaner/8725 is trying to acquire lock:
ffff0000d6826a48 (&delayed_node->mutex){+.+.}-{4:4}, at: __btrfs_release_delayed_node+0xa0/0x9b0 fs/btrfs/delayed-inode.c:290

but task is already holding lock:
ffff0000dbeba878 (btrfs-tree-00){++++}-{4:4}, at: btrfs_tree_read_lock_nested+0x44/0x2ec fs/btrfs/locking.c:145

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (btrfs-tree-00){++++}-{4:4}:
       __lock_release kernel/locking/lockdep.c:5574 [inline]
       lock_release+0x198/0x39c kernel/locking/lockdep.c:5889
       up_read+0x24/0x3c kernel/locking/rwsem.c:1632
       btrfs_tree_read_unlock+0xdc/0x298 fs/btrfs/locking.c:169
       btrfs_tree_unlock_rw fs/btrfs/locking.h:218 [inline]
       btrfs_search_slot+0xa6c/0x223c fs/btrfs/ctree.c:2133
       btrfs_lookup_inode+0xd8/0x38c fs/btrfs/inode-item.c:395
       __btrfs_update_delayed_inode+0x124/0xed0 fs/btrfs/delayed-inode.c:1032
       btrfs_update_delayed_inode fs/btrfs/delayed-inode.c:1118 [inline]
       __btrfs_commit_inode_delayed_items+0x15f8/0x1748 fs/btrfs/delayed-inode.c:1141
       __btrfs_run_delayed_items+0x1ac/0x514 fs/btrfs/delayed-inode.c:1176
       btrfs_run_delayed_items_nr+0x28/0x38 fs/btrfs/delayed-inode.c:1219
       flush_space+0x26c/0xb68 fs/btrfs/space-info.c:828
       do_async_reclaim_metadata_space+0x110/0x364 fs/btrfs/space-info.c:1158
       btrfs_async_reclaim_metadata_space+0x90/0xd8 fs/btrfs/space-info.c:1226
       process_one_work+0x7e8/0x155c kernel/workqueue.c:3263
       process_scheduled_works kernel/workqueue.c:3346 [inline]
       worker_thread+0x958/0xed8 kernel/workqueue.c:3427
       kthread+0x5fc/0x75c kernel/kthread.c:463
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

-> #0 (&delayed_node->mutex){+.+.}-{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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
       lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
       __mutex_lock_common+0x1d0/0x2678 kernel/locking/mutex.c:598
       __mutex_lock kernel/locking/mutex.c:760 [inline]
       mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812
       __btrfs_release_delayed_node+0xa0/0x9b0 fs/btrfs/delayed-inode.c:290
       btrfs_release_delayed_node fs/btrfs/delayed-inode.c:315 [inline]
       btrfs_remove_delayed_node+0x68/0x84 fs/btrfs/delayed-inode.c:1326
       btrfs_evict_inode+0x578/0xe28 fs/btrfs/inode.c:5587
       evict+0x414/0x928 fs/inode.c:810
       iput_final fs/inode.c:1914 [inline]
       iput+0x95c/0xad4 fs/inode.c:1966
       iget_failed+0xec/0x134 fs/bad_inode.c:248
       btrfs_read_locked_inode+0xe1c/0x1234 fs/btrfs/inode.c:4101
       btrfs_iget+0x1b0/0x264 fs/btrfs/inode.c:5837
       btrfs_run_defrag_inode fs/btrfs/defrag.c:237 [inline]
       btrfs_run_defrag_inodes+0x520/0xdc4 fs/btrfs/defrag.c:309
       cleaner_kthread+0x21c/0x418 fs/btrfs/disk-io.c:1516
       kthread+0x5fc/0x75c kernel/kthread.c:463
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(btrfs-tree-00);
                               lock(&delayed_node->mutex);
                               lock(btrfs-tree-00);
  lock(&delayed_node->mutex);

 *** DEADLOCK ***

1 lock held by btrfs-cleaner/8725:
 #0: ffff0000dbeba878 (btrfs-tree-00){++++}-{4:4}, at: btrfs_tree_read_lock_nested+0x44/0x2ec fs/btrfs/locking.c:145

stack backtrace:
CPU: 0 UID: 0 PID: 8725 Comm: btrfs-cleaner Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043
 check_noncircular+0x154/0x174 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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
 __mutex_lock_common+0x1d0/0x2678 kernel/locking/mutex.c:598
 __mutex_lock kernel/locking/mutex.c:760 [inline]
 mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812
 __btrfs_release_delayed_node+0xa0/0x9b0 fs/btrfs/delayed-inode.c:290
 btrfs_release_delayed_node fs/btrfs/delayed-inode.c:315 [inline]
 btrfs_remove_delayed_node+0x68/0x84 fs/btrfs/delayed-inode.c:1326
 btrfs_evict_inode+0x578/0xe28 fs/btrfs/inode.c:5587
 evict+0x414/0x928 fs/inode.c:810
 iput_final fs/inode.c:1914 [inline]
 iput+0x95c/0xad4 fs/inode.c:1966
 iget_failed+0xec/0x134 fs/bad_inode.c:248
 btrfs_read_locked_inode+0xe1c/0x1234 fs/btrfs/inode.c:4101
 btrfs_iget+0x1b0/0x264 fs/btrfs/inode.c:5837
 btrfs_run_defrag_inode fs/btrfs/defrag.c:237 [inline]
 btrfs_run_defrag_inodes+0x520/0xdc4 fs/btrfs/defrag.c:309
 cleaner_kthread+0x21c/0x418 fs/btrfs/disk-io.c:1516
 kthread+0x5fc/0x75c kernel/kthread.c:463
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:844

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/15 10:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __btrfs_release_delayed_node
* Struck through repros no longer work on HEAD.