Hello, syzbot found the following issue on:
HEAD commit: 7b1d1d4cfac0 Merge remote-tracking branch 'iommu/arm/smmu'.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=12978ec0580000 kernel config: https://syzkaller.appspot.com/x/.config?x=dfe1e340fbee3d16 dashboard link: https://syzkaller.appspot.com/bug?extid=35a21b6aade7af3c7b3a compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12f31b78580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16978ec0580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/354fe38e2935/disk-7b1d1d4c.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/f12e0b1ef3fd/vmlinux-7b1d1d4c.xz kernel image: https://storage.googleapis.com/syzbot-assets/291dbc519bb3/Image-7b1d1d4c.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/009d543e9698/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+35a21b6aade7af3c7...@syzkaller.appspotmail.com F2FS-fs (loop0): invalid crc value F2FS-fs (loop0): Found nat_bits in checkpoint F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ------------[ cut here ]------------ WARNING: CPU: 1 PID: 6420 at fs/inode.c:336 drop_nlink+0xe4/0x138 fs/inode.c:336 Modules linked in: CPU: 1 UID: 0 PID: 6420 Comm: syz-executor117 Not tainted 6.12.0-syzkaller-g7b1d1d4cfac0 #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:336 lr : drop_nlink+0xe4/0x138 fs/inode.c:336 sp : ffff8000a3d57930 x29: ffff8000a3d57930 x28: 0000000000000000 x27: dfff800000000000 x26: 0000000000000003 x25: fffffdffc363c040 x24: 1fffe0001bc77232 x23: 1fffe0001bc7723b x22: dfff800000000000 x21: 0000000000000000 x20: ffff0000de3b91d8 x19: ffff0000de3b9190 x18: ffff8000a3d57520 x17: 000000000000d842 x16: ffff800080355c58 x15: 0000000000000001 x14: 1ffff00011f440c0 x13: 0000000000000000 x12: 0000000000000000 x11: ffff700011f440c1 x10: 0000000000ff0100 x9 : 0000000000000000 x8 : ffff0000c2d80000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : ffff8000933cf888 x4 : 0000000000000004 x3 : ffff8000804807cc x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: drop_nlink+0xe4/0x138 fs/inode.c:336 (P) drop_nlink+0xe4/0x138 fs/inode.c:336 (L) f2fs_i_links_write fs/f2fs/f2fs.h:3127 [inline] f2fs_drop_nlink+0xd0/0x2ec fs/f2fs/dir.c:822 f2fs_delete_entry+0x9c8/0xcb0 fs/f2fs/dir.c:886 f2fs_unlink+0x48c/0xad8 fs/f2fs/namei.c:572 vfs_unlink+0x2f0/0x534 fs/namei.c:4469 do_unlinkat+0x4d0/0x700 fs/namei.c:4533 __do_sys_unlinkat fs/namei.c:4576 [inline] __se_sys_unlinkat fs/namei.c:4569 [inline] __arm64_sys_unlinkat+0xc8/0xf8 fs/namei.c:4569 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 irq event stamp: 212352 hardirqs last enabled at (212351): [<ffff80008047a5a4>] seqcount_lockdep_reader_access+0x80/0x104 include/linux/seqlock.h:74 hardirqs last disabled at (212352): [<ffff80008b4b302c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:488 softirqs last enabled at (212312): [<ffff80008020396c>] softirq_handle_end kernel/softirq.c:400 [inline] softirqs last enabled at (212312): [<ffff80008020396c>] handle_softirqs+0xa38/0xbf8 kernel/softirq.c:582 softirqs last disabled at (212299): [<ffff800080020db4>] __do_softirq+0x14/0x20 kernel/softirq.c:588 ---[ 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 syzkal...@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 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. 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 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
