syzbot


kernel BUG in clear_inode (4)

Status: upstream: reported C repro on 2025/09/09 21:11
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com
Fix commit: 9251a9e6e871 f2fs: fix to truncate first page in error path of f2fs_truncate()
Patched on: [ci-qemu-gce-upstream-auto 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-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-linux-next-kasan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci-upstream-rust-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb], missing on: [ci-qemu-native-arm64-kvm ci-upstream-gce-arm64]
First crash: 31d, last: 3h21m
Cause bisection: introduced by (bisect log) :
commit c240c87bcd44a1a2375fc8ef8c645d1f1fe76466
Author: Chao Yu <chao@kernel.org>
Date: Tue May 21 06:23:18 2024 +0000

  f2fs: fix to do sanity check on blocks for inline_data inode

Crash: kernel BUG in clear_inode (log)
Repro: C syz .config
  
Discussions (2)
Title Replies (including bot) Last reply
[PATCH] f2fs: fix to truncate first page in error path of f2fs_truncate() 2 (2) 2025/09/29 22:30
[syzbot] [f2fs?] kernel BUG in clear_inode (4) 1 (4) 2025/09/10 08:25
Similar bugs (9)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG in clear_inode (2) jfs -1 C inconclusive 986 122d 347d 28/29 fixed on 2025/06/10 16:19
linux-6.1 kernel BUG in clear_inode origin:upstream missing-backport -1 C inconclusive 28 55d 869d 0/3 upstream: reported C repro on 2023/05/25 23:24
linux-6.6 kernel BUG in clear_inode origin:upstream missing-backport -1 C inconclusive 6 55d 115d 0/2 upstream: reported C repro on 2025/06/18 00:00
linux-5.15 kernel BUG in clear_inode (3) missing-backport origin:lts-only -1 C done 25 32d 323d 0/3 upstream: reported C repro on 2024/11/22 00:29
linux-5.15 kernel BUG in clear_inode -1 1 893d 893d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:07
upstream kernel BUG in clear_inode (3) jfs -1 C error 637 39d 120d 29/29 fixed on 2025/09/04 16:57
linux-5.15 kernel BUG in clear_inode (2) -1 2 448d 527d 0/3 auto-obsoleted due to no activity on 2024/10/27 05:50
upstream kernel BUG in clear_inode btrfs -1 C 12 355d 497d 28/29 fixed on 2024/10/22 11:57
upstream kernel BUG at fs/inode.c:LINE! (2) fs -1 C done unreliable 322 521d 1869d 25/29 fixed on 2024/05/21 07:00
Last patch testing requests (3)
Created Duration User Patch Repo Result
2025/09/27 22:15 13m retest repro upstream report log
2025/09/27 22:15 14m retest repro upstream report log
2025/09/10 07:58 23m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/syzbot OK log

Sample crash report:
loop0: detected capacity change from 0 to 40427
F2FS-fs (loop0): Wrong SSA boundary, start(3584) end(4096) blocks(3072)
F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): f2fs_convert_inline_folio: corrupted inline inode ino=3, i_addr[0]:0x1601, run fsck to fix.
------------[ cut here ]------------
kernel BUG at fs/inode.c:753!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6097 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:clear_inode+0x169/0x190 fs/inode.c:753
Code: 4c 89 f7 e8 59 7a ec ff e9 60 ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 7c c0 4c 89 f7 e8 2f 7b ec ff eb b6 e8 28 40 8d ff 90 <0f> 0b e8 20 40 8d ff 90 0f 0b e8 18 40 8d ff 90 0f 0b e8 10 40 8d
RSP: 0018:ffffc9000408f890 EFLAGS: 00010293
RAX: ffffffff82311f78 RBX: ffff888022059300 RCX: ffff888024ced940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000408fa00 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1e3ab47 R12: dffffc0000000000
R13: ffff888022059300 R14: ffff888022059558 R15: 0000000000000001
FS:  000055557dd70500(0000) GS:ffff8881268bf000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055738e9e8660 CR3: 0000000029a1c000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 evict+0x504/0x9c0 fs/inode.c:810
 f2fs_fill_super+0x5612/0x6fa0 fs/f2fs/super.c:5047
 get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1692
 vfs_get_tree+0x8f/0x2b0 fs/super.c:1815
 do_new_mount+0x2a2/0x9e0 fs/namespace.c:3808
 do_mount fs/namespace.c:4136 [inline]
 __do_sys_mount fs/namespace.c:4347 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4324
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f865d77038a
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:00007ffc62ec72e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc62ec7370 RCX: 00007f865d77038a
RDX: 0000200000000140 RSI: 00002000000000c0 RDI: 00007ffc62ec7330
RBP: 0000200000000140 R08: 00007ffc62ec7370 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000246 R12: 00002000000000c0
R13: 00007ffc62ec7330 R14: 0000000000005531 R15: 00002000000056c0
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:clear_inode+0x169/0x190 fs/inode.c:753
Code: 4c 89 f7 e8 59 7a ec ff e9 60 ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 7c c0 4c 89 f7 e8 2f 7b ec ff eb b6 e8 28 40 8d ff 90 <0f> 0b e8 20 40 8d ff 90 0f 0b e8 18 40 8d ff 90 0f 0b e8 10 40 8d
RSP: 0018:ffffc9000408f890 EFLAGS: 00010293
RAX: ffffffff82311f78 RBX: ffff888022059300 RCX: ffff888024ced940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000408fa00 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1e3ab47 R12: dffffc0000000000
R13: ffff888022059300 R14: ffff888022059558 R15: 0000000000000001
FS:  000055557dd70500(0000) GS:ffff8881268bf000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055738e9e8660 CR3: 0000000029a1c000 CR4: 00000000003526f0

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/09 12:33 upstream f777d1112ee5 d291dd2d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs kernel BUG in clear_inode
2025/09/09 11:53 upstream f777d1112ee5 d291dd2d .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root kernel BUG in clear_inode
2025/09/09 11:41 upstream f777d1112ee5 d291dd2d .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root kernel BUG in clear_inode
2025/10/10 21:55 upstream 917167ed1211 ff1712fe .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel BUG in clear_inode
2025/09/13 21:41 upstream 5cd64d4f9268 e2beed91 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel BUG in clear_inode
2025/09/09 11:29 upstream f777d1112ee5 d291dd2d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root kernel BUG in clear_inode
* Struck through repros no longer work on HEAD.