syzbot


possible deadlock in bd_prepare_to_claim

Status: upstream: reported on 2025/07/17 00:57
Reported-by: syzbot+c6b56897158c5958d596@syzkaller.appspotmail.com
First crash: 42d, last: 4d07h
Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in bd_prepare_to_claim block 4 15 648d 699d 0/29 auto-obsoleted due to no activity on 2024/01/27 23:26

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.6.102-syzkaller #0 Not tainted
------------------------------------------------------
syz.0.11660/16410 is trying to acquire lock:
ffffffff8ca648e8 (bdev_lock){+.+.}-{3:3}, at: bd_prepare_to_claim+0x1ba/0x480 block/bdev.c:510

but task is already holding lock:
ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:849 [inline]
ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:187 [inline]
ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1b7c/0x23d0 block/ioctl.c:513

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (mapping.invalidate_lock#2){++++}-{3:3}:
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
       filemap_invalidate_lock_shared include/linux/fs.h:859 [inline]
       page_cache_ra_unbounded+0xdc/0x770 mm/readahead.c:225
       page_cache_sync_readahead include/linux/pagemap.h:1325 [inline]
       ext4_readdir+0xb71/0x39d0 fs/ext4/dir.c:197
       iterate_dir+0x1c2/0x580 fs/readdir.c:106
       ovl_dir_read+0xfc/0x560 fs/overlayfs/readdir.c:309
       ovl_check_d_type_supported+0x99/0x100 fs/overlayfs/readdir.c:1065
       ovl_make_workdir fs/overlayfs/super.c:733 [inline]
       ovl_get_workdir+0x487/0x1740 fs/overlayfs/super.c:874
       ovl_fill_super+0x1345/0x3560 fs/overlayfs/super.c:1427
       vfs_get_super fs/super.c:1346 [inline]
       get_tree_nodev+0xb5/0x140 fs/super.c:1365
       vfs_get_tree+0x8c/0x280 fs/super.c:1764
       do_new_mount+0x24b/0xa40 fs/namespace.c:3371
       do_mount fs/namespace.c:3711 [inline]
       __do_sys_mount fs/namespace.c:3920 [inline]
       __se_sys_mount+0x2da/0x3c0 fs/namespace.c:3897
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #3 (&type->i_mutex_dir_key#3){++++}-{3:3}:
       down_write+0x97/0x1f0 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:804 [inline]
       ext4_process_orphan+0x187/0x300 fs/ext4/orphan.c:337
       ext4_orphan_cleanup+0xbd4/0x1400 fs/ext4/orphan.c:474
       __ext4_fill_super fs/ext4/super.c:5606 [inline]
       ext4_fill_super+0x5d47/0x6620 fs/ext4/super.c:5729
       get_tree_bdev+0x3e4/0x510 fs/super.c:1591
       vfs_get_tree+0x8c/0x280 fs/super.c:1764
       do_new_mount+0x24b/0xa40 fs/namespace.c:3371
       do_mount fs/namespace.c:3711 [inline]
       __do_sys_mount fs/namespace.c:3920 [inline]
       __se_sys_mount+0x2da/0x3c0 fs/namespace.c:3897
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (&type->s_umount_key#31){++++}-{3:3}:
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
       __super_lock fs/super.c:58 [inline]
       super_lock+0x167/0x360 fs/super.c:117
       super_lock_shared fs/super.c:146 [inline]
       super_lock_shared_active fs/super.c:1442 [inline]
       fs_bdev_sync+0xa4/0x170 fs/super.c:1477
       blkdev_flushbuf block/ioctl.c:375 [inline]
       blkdev_common_ioctl+0x880/0x23d0 block/ioctl.c:505
       blkdev_ioctl+0x4eb/0x6f0 block/ioctl.c:627
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&bdev->bd_holder_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       bd_finish_claiming+0x22f/0x3f0 block/bdev.c:568
       blkdev_get_by_dev+0x45c/0x600 block/bdev.c:801
       bdev_open_by_dev+0x77/0x100 block/bdev.c:842
       setup_bdev_super+0x59/0x660 fs/super.c:1496
       mount_bdev+0x1dd/0x2d0 fs/super.c:1640
       legacy_get_tree+0xea/0x180 fs/fs_context.c:662
       vfs_get_tree+0x8c/0x280 fs/super.c:1764
       do_new_mount+0x24b/0xa40 fs/namespace.c:3371
       init_mount+0xd2/0x120 fs/init.c:25
       do_mount_root+0x97/0x230 init/do_mounts.c:166
       mount_root_generic+0x195/0x3c0 init/do_mounts.c:205
       prepare_namespace+0xc2/0x100 init/do_mounts.c:489
       kernel_init_freeable+0x413/0x570 init/main.c:1566
       kernel_init+0x1d/0x1c0 init/main.c:1443
       ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
       ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293

-> #0 (bdev_lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
       lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
       bd_prepare_to_claim+0x1ba/0x480 block/bdev.c:510
       truncate_bdev_range+0x4e/0x260 block/bdev.c:105
       blk_ioctl_zeroout block/ioctl.c:188 [inline]
       blkdev_common_ioctl+0x1b92/0x23d0 block/ioctl.c:513
       blkdev_ioctl+0x4eb/0x6f0 block/ioctl.c:627
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  bdev_lock --> &type->i_mutex_dir_key#3 --> mapping.invalidate_lock#2

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(mapping.invalidate_lock#2);
                               lock(&type->i_mutex_dir_key#3);
                               lock(mapping.invalidate_lock#2);
  lock(bdev_lock);

 *** DEADLOCK ***

1 lock held by syz.0.11660/16410:
 #0: ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:849 [inline]
 #0: ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:187 [inline]
 #0: ffff88801ff87c40 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1b7c/0x23d0 block/ioctl.c:513

stack backtrace:
CPU: 0 PID: 16410 Comm: syz.0.11660 Not tainted 6.6.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_noncircular+0x2bd/0x3c0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x129/0xcc0 kernel/locking/mutex.c:747
 bd_prepare_to_claim+0x1ba/0x480 block/bdev.c:510
 truncate_bdev_range+0x4e/0x260 block/bdev.c:105
 blk_ioctl_zeroout block/ioctl.c:188 [inline]
 blkdev_common_ioctl+0x1b92/0x23d0 block/ioctl.c:513
 blkdev_ioctl+0x4eb/0x6f0 block/ioctl.c:627
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:871 [inline]
 __se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f91d7d8ebe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f91d8cb1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f91d7fb5fa0 RCX: 00007f91d7d8ebe9
RDX: 0000200000000240 RSI: 000000000000127f RDI: 0000000000000003
RBP: 00007f91d7e11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f91d7fb6038 R14: 00007f91d7fb5fa0 R15: 00007fffa6df3478
 </TASK>

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/24 00:27 linux-6.6.y bb9c90ab9c5a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/22 18:41 linux-6.6.y bb9c90ab9c5a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/08 20:13 linux-6.6.y 3a8ababb8b6a 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/07 01:55 linux-6.6.y 3a8ababb8b6a 9a42d6b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/06 02:49 linux-6.6.y 3a8ababb8b6a ffe1dd46 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/05 17:49 linux-6.6.y 3a8ababb8b6a 37880f40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/05 17:48 linux-6.6.y 3a8ababb8b6a 37880f40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/05 00:44 linux-6.6.y 3a8ababb8b6a f5bcc8dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/08/05 00:43 linux-6.6.y 3a8ababb8b6a f5bcc8dc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
2025/07/17 00:57 linux-6.6.y 9247f4e6573a 44f8051e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan possible deadlock in bd_prepare_to_claim
* Struck through repros no longer work on HEAD.