[v5.15] WARNING in f2fs_rename2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4735586da88e Linux 5.15.176
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14c8eef8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=caf0c22a63c5c861
dashboard link: https://syzkaller.appspot.com/bug?extid=2b4f6d1a0417159cef1d
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/3e7a2d136136/disk-4735586d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7597375cf469/vmlinux-4735586d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/132474c9ad82/Image-4735586d.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5526 at fs/inode.c:307 drop_nlink+0xe8/0x148 fs/inode.c:307
Modules linked in:
CPU: 1 PID: 5526 Comm: syz.4.306 Not tainted 5.15.176-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+0xe8/0x148 fs/inode.c:307
lr : drop_nlink+0xe8/0x148 fs/inode.c:307
sp : ffff80001fbd7620
x29: ffff80001fbd7620 x28: ffff80001fbd7780 x27: 1fffe0001d2715f0
x26: dfff800000000000 x25: ffff0000e938c2f8 x24: 0000000002b00e09
x23: 1fffe0001d271859 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e938c2c8 x19: ffff0000e938c280 x18: ffff80001fbd7340
x17: 0000000000000002 x16: ffff8000082e5510 x15: 000000000003610b
x14: ffff8000171f0500 x13: dfff800000000000 x12: 0000000000080000
x11: 000000000000c39d x10: ffff800025739000 x9 : 000000000000c39e
x8 : ffff8000089e9c90 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff8000082e5758
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe8/0x148 fs/inode.c:307
f2fs_i_links_write fs/f2fs/f2fs.h:2884 [inline]
f2fs_rename fs/f2fs/namei.c:972 [inline]
f2fs_rename2+0x1424/0x200c fs/f2fs/namei.c:1246
vfs_rename+0xac8/0xe04 fs/namei.c:4832
do_renameat2+0xa00/0x10c0 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 440354
hardirqs last enabled at (440353): [<ffff8000083c6d88>] seqcount_lockdep_reader_access+0x208/0x2cc include/linux/seqlock.h:105
hardirqs last disabled at (440354): [<ffff800011b478f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (440182): [<ffff8000080309b8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (440180): [<ffff800008030984>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 97bb8a7f4f4ed230 ]---


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

syzbot has found a reproducer for the following issue on:

HEAD commit: 4735586da88e Linux 5.15.176
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10ada218580000

kernel config: https://syzkaller.appspot.com/x/.config?x=caf0c22a63c5c861
dashboard link: https://syzkaller.appspot.com/bug?extid=2b4f6d1a0417159cef1d
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=155b53c4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=102421df980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3e7a2d136136/disk-4735586d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7597375cf469/vmlinux-4735586d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/132474c9ad82/Image-4735586d.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/88d8af6a697d/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2b4f6d...@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: 0 PID: 4019 at fs/inode.c:307 drop_nlink+0xe8/0x148 fs/inode.c:307
Modules linked in:
CPU: 0 PID: 4019 Comm: syz-executor782 Not tainted 5.15.176-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+0xe8/0x148 fs/inode.c:307
lr : drop_nlink+0xe8/0x148 fs/inode.c:307

sp : ffff80001df47620
x29: ffff80001df47620 x28: ffff80001df47780 x27: 1fffe0001c3a6000
x26: dfff800000000000 x25: ffff0000e1d309f8 x24: 000000001e65fb80
x23: 1fffe0001c3a6139 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e1d309c8 x19: ffff0000e1d30980 x18: ffff80001df47340
x17: 0000000000000000 x16: ffff8000082e5510 x15: 000000000000bd3a
x14: 0000000081c84cb1 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c9453680

x8 : ffff8000089e9c90 x7 : 0000000000000000 x6 : 0000000000000000

x5 : ffff800017847060 x4 : 0000000000000002 x3 : ffff8000082e5758

x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe8/0x148 fs/inode.c:307
f2fs_i_links_write fs/f2fs/f2fs.h:2884 [inline]
f2fs_rename fs/f2fs/namei.c:972 [inline]
f2fs_rename2+0x1424/0x200c fs/f2fs/namei.c:1246
vfs_rename+0xac8/0xe04 fs/namei.c:4832
do_renameat2+0xa00/0x10c0 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

irq event stamp: 284236
hardirqs last enabled at (284235): [<ffff8000083c6d88>] seqcount_lockdep_reader_access+0x208/0x2cc include/linux/seqlock.h:105
hardirqs last disabled at (284236): [<ffff800011b478f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (283770): [<ffff8000080309b8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (283768): [<ffff800008030984>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace d93e4209fcb50389 ]---


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