[v6.6] possible deadlock in ext4_process_orphan
0 views
Skip to first unread message
syzbot
Aug 5, 2025, 10:51:28 PM8/5/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3a8ababb8b6a Linux 6.6.101
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=130696a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2bd95b6de4839b7
dashboard link: https://syzkaller.appspot.com/bug?extid=30f7a3132b5a5f1e212c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f06c672f5fa8/disk-3a8ababb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9af9b7afcdc5/vmlinux-3a8ababb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/351a55aafa77/bzImage-3a8ababb.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+30f7a3...@syzkaller.appspotmail.com
loop9: detected capacity change from 0 to 512
EXT4-fs (loop9): encrypted files will use data=ordered instead of data journaling mode
======================================================
WARNING: possible circular locking dependency detected
6.6.101-syzkaller #0 Not tainted
------------------------------------------------------
syz.9.1916/11883 is trying to acquire lock:
ffff88805b4a7210 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
ffff88805b4a7210 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: ext4_process_orphan+0x187/0x300 fs/ext4/orphan.c:337
but task is already holding lock:
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: get_tree_bdev+0x344/0x510 fs/super.c:1589
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (&type->s_umount_key#32){++++}-{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
-> #3 (&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
-> #2 (bdev_lock){+.+.}-{3:3}:
__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
blkdev_fallocate+0x3ff/0x670 block/fops.c:792
vfs_fallocate+0x58e/0x700 fs/open.c:324
madvise_remove mm/madvise.c:1007 [inline]
madvise_vma_behavior mm/madvise.c:1031 [inline]
madvise_walk_vmas mm/madvise.c:1266 [inline]
do_madvise+0x15fe/0x3710 mm/madvise.c:1446
__do_sys_madvise mm/madvise.c:1459 [inline]
__se_sys_madvise mm/madvise.c:1457 [inline]
__x64_sys_madvise+0xa6/0xc0 mm/madvise.c:1457
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 (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
-> #0 (&type->i_mutex_dir_key#3){++++}-{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
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
other info that might help us debug this:
Chain exists of:
&type->i_mutex_dir_key#3 --> &bdev->bd_holder_lock --> &type->s_umount_key#32
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&type->s_umount_key#32);
lock(&bdev->bd_holder_lock);
lock(&type->s_umount_key#32);
lock(&type->i_mutex_dir_key#3);
*** DEADLOCK ***
1 lock held by syz.9.1916/11883:
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: get_tree_bdev+0x344/0x510 fs/super.c:1589
stack backtrace:
CPU: 1 PID: 11883 Comm: syz.9.1916 Not tainted 6.6.101-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
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
RIP: 0033:0x7f09c4b9038a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f09c5ac3e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f09c5ac3ef0 RCX: 00007f09c4b9038a
RDX: 0000200000000040 RSI: 0000200000000180 RDI: 00007f09c5ac3eb0
RBP: 0000200000000040 R08: 00007f09c5ac3ef0 R09: 000000000000000e
R10: 000000000000000e R11: 0000000000000246 R12: 0000200000000180
R13: 00007f09c5ac3eb0 R14: 0000000000000451 R15: 00002000000004c0
</TASK>
EXT4-fs (loop9): 1 truncate cleaned up
EXT4-fs (loop9): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 3a8ababb8b6a Linux 6.6.101
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=130696a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2bd95b6de4839b7
dashboard link: https://syzkaller.appspot.com/bug?extid=30f7a3132b5a5f1e212c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f06c672f5fa8/disk-3a8ababb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9af9b7afcdc5/vmlinux-3a8ababb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/351a55aafa77/bzImage-3a8ababb.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+30f7a3...@syzkaller.appspotmail.com
loop9: detected capacity change from 0 to 512
EXT4-fs (loop9): encrypted files will use data=ordered instead of data journaling mode
======================================================
WARNING: possible circular locking dependency detected
6.6.101-syzkaller #0 Not tainted
------------------------------------------------------
syz.9.1916/11883 is trying to acquire lock:
ffff88805b4a7210 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
ffff88805b4a7210 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: ext4_process_orphan+0x187/0x300 fs/ext4/orphan.c:337
but task is already holding lock:
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: get_tree_bdev+0x344/0x510 fs/super.c:1589
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #4 (&type->s_umount_key#32){++++}-{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
-> #3 (&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
-> #2 (bdev_lock){+.+.}-{3:3}:
__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
blkdev_fallocate+0x3ff/0x670 block/fops.c:792
vfs_fallocate+0x58e/0x700 fs/open.c:324
madvise_remove mm/madvise.c:1007 [inline]
madvise_vma_behavior mm/madvise.c:1031 [inline]
madvise_walk_vmas mm/madvise.c:1266 [inline]
do_madvise+0x15fe/0x3710 mm/madvise.c:1446
__do_sys_madvise mm/madvise.c:1459 [inline]
__se_sys_madvise mm/madvise.c:1457 [inline]
__x64_sys_madvise+0xa6/0xc0 mm/madvise.c:1457
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 (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
-> #0 (&type->i_mutex_dir_key#3){++++}-{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
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
other info that might help us debug this:
Chain exists of:
&type->i_mutex_dir_key#3 --> &bdev->bd_holder_lock --> &type->s_umount_key#32
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&type->s_umount_key#32);
lock(&bdev->bd_holder_lock);
lock(&type->s_umount_key#32);
lock(&type->i_mutex_dir_key#3);
*** DEADLOCK ***
1 lock held by syz.9.1916/11883:
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880300860e0 (&type->s_umount_key#32){++++}-{3:3}, at: get_tree_bdev+0x344/0x510 fs/super.c:1589
stack backtrace:
CPU: 1 PID: 11883 Comm: syz.9.1916 Not tainted 6.6.101-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
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
RIP: 0033:0x7f09c4b9038a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f09c5ac3e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f09c5ac3ef0 RCX: 00007f09c4b9038a
RDX: 0000200000000040 RSI: 0000200000000180 RDI: 00007f09c5ac3eb0
RBP: 0000200000000040 R08: 00007f09c5ac3ef0 R09: 000000000000000e
R10: 000000000000000e R11: 0000000000000246 R12: 0000200000000180
R13: 00007f09c5ac3eb0 R14: 0000000000000451 R15: 00002000000004c0
</TASK>
EXT4-fs (loop9): 1 truncate cleaned up
EXT4-fs (loop9): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none.
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot
Jan 9, 2026, 11:00:17 AMJan 9
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages