[v6.6] kernel BUG in clear_inode

4 views
Skip to first unread message

syzbot

unread,
Jun 17, 2025, 8:00:37 PM6/17/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13f9b50c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=104f5ed9af31229ee2ef
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+104f5e...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/inode.c:650!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 22334 Comm: syz-executor Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:clear_inode+0x12c/0x150 fs/inode.c:650
Code: e8 89 92 91 ff 43 80 3c 27 00 74 08 4c 89 f7 e8 0a 38 ea ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 64 92 91 ff <0f> 0b e8 5d 92 91 ff 0f 0b e8 56 92 91 ff 0f 0b e8 4f 92 91 ff 0f
RSP: 0018:ffffc9000338f970 EFLAGS: 00010093
RAX: ffffffff81f4047c RBX: ffff88805aa80d70 RCX: ffff88802cfa1e00
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000671f0c R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805aa80fa0 R15: 0000000000000011
FS: 0000555570bf4500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f28a1570000 CR3: 000000006b0b4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000004144
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_evict_inode+0xb1/0x440 fs/jfs/inode.c:166
evict+0x486/0x870 fs/inode.c:705
__dentry_kill+0x431/0x650 fs/dcache.c:611
shrink_dentry_list+0x39f/0x6a0 fs/dcache.c:1206
shrink_dcache_parent+0xac/0x3c0 fs/dcache.c:-1
do_one_tree+0x23/0xe0 fs/dcache.c:1686
shrink_dcache_for_umount+0x69/0x110 fs/dcache.c:1703
generic_shutdown_super+0x67/0x2b0 fs/super.c:665
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f762298fc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc8c301c28 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f7622a10925 RCX: 00007f762298fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc8c301ce0
RBP: 00007ffc8c301ce0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc8c302d70
R13: 00007f7622a10925 R14: 0000000000119454 R15: 00007ffc8c302db0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:clear_inode+0x12c/0x150 fs/inode.c:650
Code: e8 89 92 91 ff 43 80 3c 27 00 74 08 4c 89 f7 e8 0a 38 ea ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 64 92 91 ff <0f> 0b e8 5d 92 91 ff 0f 0b e8 56 92 91 ff 0f 0b e8 4f 92 91 ff 0f
RSP: 0018:ffffc9000338f970 EFLAGS: 00010093
RAX: ffffffff81f4047c RBX: ffff88805aa80d70 RCX: ffff88802cfa1e00
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000671f0c R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805aa80fa0 R15: 0000000000000011
FS: 0000555570bf4500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f28a1570000 CR3: 000000006b0b4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000004144
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400


---
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

unread,
Jun 18, 2025, 5:09:27 AM6/18/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1440a370580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=104f5ed9af31229ee2ef
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a7f90c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1227de82580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/60969ceb6344/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1250f50c580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+104f5e...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/inode.c:650!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5770 Comm: syz-executor231 Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:clear_inode+0x12c/0x150 fs/inode.c:650
Code: e8 89 92 91 ff 43 80 3c 27 00 74 08 4c 89 f7 e8 0a 38 ea ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 64 92 91 ff <0f> 0b e8 5d 92 91 ff 0f 0b e8 56 92 91 ff 0f 0b e8 4f 92 91 ff 0f
RSP: 0018:ffffc900043ef970 EFLAGS: 00010093
RAX: ffffffff81f4047c RBX: ffff88807521a930 RCX: ffff88807a910000
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200087df0c R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88807521ab60 R15: 0000000000000011
FS: 00005555688b7380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdd5d86fa8 CR3: 0000000021c5b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_evict_inode+0xb1/0x440 fs/jfs/inode.c:166
evict+0x486/0x870 fs/inode.c:705
__dentry_kill+0x431/0x650 fs/dcache.c:611
shrink_dentry_list+0x39f/0x6a0 fs/dcache.c:1206
shrink_dcache_parent+0xac/0x3c0 fs/dcache.c:-1
do_one_tree+0x23/0xe0 fs/dcache.c:1686
shrink_dcache_for_umount+0x69/0x110 fs/dcache.c:1703
generic_shutdown_super+0x67/0x2b0 fs/super.c:665
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa498125607
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffdd5d87758 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000015c06 RCX: 00007fa498125607
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffdd5d87810
RBP: 00007ffdd5d87810 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffdd5d88880
R13: 00005555688b86c0 R14: 431bde82d7b634db R15: 00007ffdd5d888a0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:clear_inode+0x12c/0x150 fs/inode.c:650
Code: e8 89 92 91 ff 43 80 3c 27 00 74 08 4c 89 f7 e8 0a 38 ea ff 49 c7 06 60 00 00 00 5b 41 5c 41 5d 41 5e 41 5f c3 e8 64 92 91 ff <0f> 0b e8 5d 92 91 ff 0f 0b e8 56 92 91 ff 0f 0b e8 4f 92 91 ff 0f
RSP: 0018:ffffc900043ef970 EFLAGS: 00010093
RAX: ffffffff81f4047c RBX: ffff88807521a930 RCX: ffff88807a910000
RDX: 0000000000000000 RSI: 0000000000000011 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff5200087df0c R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88807521ab60 R15: 0000000000000011
FS: 00005555688b7380(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdd5d86fa8 CR3: 0000000021c5b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages