Hello,
syzbot found the following issue on:
HEAD commit: b67dc5c9ade9 Linux 6.1.118
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11fb8ec0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=574f3f177f1573fa
dashboard link:
https://syzkaller.appspot.com/bug?extid=4ecfc6dcd5172a23fc28
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/7bb54d7e4cde/disk-b67dc5c9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/884b8b3180c7/vmlinux-b67dc5c9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/476257459caa/Image-b67dc5c9.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4ecfc6...@syzkaller.appspotmail.com
F2FS-fs (loop3): invalid crc value
F2FS-fs (loop3): Found nat_bits in checkpoint
F2FS-fs (loop3): Mounted with checkpoint version = 48b305e4
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4402 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4402 Comm: syz.3.8 Not tainted 6.1.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : drop_nlink+0xe4/0x138 fs/inode.c:332
lr : drop_nlink+0xe4/0x138 fs/inode.c:332
sp : ffff800021607920
x29: ffff800021607920 x28: dfff800000000000 x27: dfff800000000000
x26: ffff0000f575c000 x25: 1fffe0001e933470 x24: ffff0000f499a3f8
x23: 1fffe0001e933479 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000f499a3c8 x19: ffff0000f499a380 x18: ffff800021607560
x17: ffff800018aab000 x16: ffff800008300db8 x15: ffff80001858bf80
x14: ffff0000d79741f8 x13: dfff800000000000 x12: 0000000000080000
x11: 000000000000e61e x10: ffff80002396c000 x9 : ffff800008aaad30
x8 : 000000000000e61f x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000006 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
f2fs_i_links_write fs/f2fs/f2fs.h:3044 [inline]
f2fs_drop_nlink+0x110/0x34c fs/f2fs/dir.c:899
f2fs_delete_entry+0xae4/0xefc fs/f2fs/dir.c:966
f2fs_unlink+0x4b8/0xbdc fs/f2fs/namei.c:562
vfs_unlink+0x2f0/0x508 fs/namei.c:4322
do_unlinkat+0x4cc/0x70c fs/namei.c:4390
__do_sys_unlinkat fs/namei.c:4433 [inline]
__se_sys_unlinkat fs/namei.c:4426 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4426
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 279280
hardirqs last enabled at (279279): [<ffff800008403650>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (279279): [<ffff800008403650>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (279280): [<ffff8000122919a4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (279146): [<ffff800008030310>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (279144): [<ffff8000080302dc>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
---
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