[v6.1] WARNING in inc_nlink

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170609e9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ccbc3d5467efd1
dashboard link: https://syzkaller.appspot.com/bug?extid=2ee36b6d338031644562
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7fe538fc87bf/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8df93997601a/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/03ad7e3bf859/Image-543aff19.gz.xz

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

loop3: detected capacity change from 0 to 512
EXT2-fs (loop3): warning: mounting ext3 filesystem as ext2
------------[ cut here ]------------
WARNING: CPU: 0 PID: 15049 at fs/inode.c:387 inc_nlink+0x128/0x154 fs/inode.c:387
Modules linked in:
CPU: 0 PID: 15049 Comm: syz-executor.3 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : inc_nlink+0x128/0x154 fs/inode.c:387
lr : inc_nlink+0x128/0x154 fs/inode.c:387
sp : ffff800021287b60
x29: ffff800021287b60 x28: dfff800000000000 x27: 0000000000000000
x26: 1fffe0001b01cb4b x25: ffff800012356cc8 x24: 0000000000000000
x23: 1fffe00025cd6030 x22: dfff800000000000 x21: 0000000000000000
x20: ffff00012e6b0138 x19: ffff00012e6b0180 x18: ffff8000212873c0
x17: ffff80001557d000 x16: ffff80001202a700 x15: 0000000000000000
x14: 00000000ffff8000 x13: 00000000d09af8b1 x12: 0000000000040000
x11: 000000000000f092 x10: ffff800028821000 x9 : ffff800008a991d4
x8 : 000000000000f093 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
inc_nlink+0x128/0x154 fs/inode.c:387
inode_inc_link_count include/linux/fs.h:2511 [inline]
ext2_mkdir+0x54/0x1e4 fs/ext2/namei.c:238
vfs_mkdir+0x334/0x4e4 fs/namei.c:4036
do_mkdirat+0x20c/0x610 fs/namei.c:4061
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4074
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
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:581
irq event stamp: 3718
hardirqs last enabled at (3717): [<ffff8000089660fc>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:242
hardirqs last disabled at (3718): [<ffff8000120d75ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (3654): [<ffff800008032b74>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (3652): [<ffff800008032b40>] 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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.