[v5.15] WARNING in drop_nlink

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d7af3e5ba454 Linux 5.15.115
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=134bba3b280000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b527a384742ac24
dashboard link: https://syzkaller.appspot.com/bug?extid=dfeb6a89bfe7b591c73a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f60865280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ae0463280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/05a22ee14f2f/disk-d7af3e5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b062fea2e542/vmlinux-d7af3e5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/14b4cea9b6c8/bzImage-d7af3e5b.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f3b067d0e0ae/mount_0.gz

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

loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3536 at fs/inode.c:307 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 1 PID: 3536 Comm: syz-executor411 Not tainted 5.15.115-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:307
Code: 49 8b 1e 48 8d bb c8 07 00 00 be 08 00 00 00 e8 ab b3 ed ff f0 48 ff 83 c8 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 55 57 a4 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90002d4f930 EFLAGS: 00010293
RAX: ffffffff81dba1fb RBX: 1ffff11003a401ef RCX: ffff888024619dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81dba17f R09: fffff520005a9e89
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801d200f78
R13: ffff888075f52928 R14: ffff88801d200f30 R15: dffffc0000000000
FS: 00007faf14253700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200028c4 CR3: 00000000135f8000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hfsplus_unlink+0x3fa/0x7f0 fs/hfsplus/dir.c:381
hfsplus_rename+0xc4/0x1b0 fs/hfsplus/dir.c:547
vfs_rename+0xd8f/0x1190 fs/namei.c:4736
do_renameat2+0xb97/0x13b0 fs/namei.c:4887
__do_sys_rename fs/namei.c:4933 [inline]
__se_sys_rename fs/namei.c:4931 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4931
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7faf142a7559
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007faf142532f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007faf142a7559
RDX: ffffffffffffffb8 RSI: 00000000200028c0 RDI: 00000000200000c0
RBP: 00007faf1432c788 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007faf1432c780
R13: 0000000020000cc0 R14: 0031656c69662f2e R15: 0073756c70736668
</TASK>


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2f3918bc53fb Linux 6.1.33
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1399e263280000
kernel config: https://syzkaller.appspot.com/x/.config?x=668ab7dd51e152ad
dashboard link: https://syzkaller.appspot.com/bug?extid=d83590f7f75c5a703ea3

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148adef1280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111791f1280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/148750653b59/disk-2f3918bc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f86efd682b25/vmlinux-2f3918bc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/483386a4e270/bzImage-2f3918bc.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e89d4b89bd34/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+d83590...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 1024
------------[ cut here ]------------

WARNING: CPU: 0 PID: 3587 at fs/inode.c:330 drop_nlink+0xbb/0x100
Modules linked in:
CPU: 0 PID: 3587 Comm: syz-executor404 Not tainted 6.1.33-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023

RIP: 0010:drop_nlink+0xbb/0x100 fs/inode.c:330
Code: 49 8b 1e 48 8d bb c0 07 00 00 be 08 00 00 00 e8 6b 41 ea ff f0 48 ff 83 c0 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 35 f8 93 ff <0f> 0b eb 89 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc90003b1f930 EFLAGS: 00010293
RAX: ffffffff81f5dd1b RBX: 1ffff1100f7e1e97 RCX: ffff888021c58000

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffffff81f5dc9f R09: fffff52000763e89
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807bf0f4b8
R13: ffff888073473370 R14: ffff88807bf0f470 R15: dffffc0000000000
FS: 00007f6117c17700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00000000200028c4 CR3: 0000000026ed5000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hfsplus_unlink+0x3fa/0x7f0 fs/hfsplus/dir.c:381
hfsplus_rename+0xc4/0x1b0 fs/hfsplus/dir.c:547

vfs_rename+0xd8f/0x1190 fs/namei.c:4779
do_renameat2+0xb97/0x13b0 fs/namei.c:4930
__do_sys_rename fs/namei.c:4976 [inline]
__se_sys_rename fs/namei.c:4974 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:4974

do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80

entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6117c6b559

Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007f6117c172f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 000000000000001f RCX: 00007f6117c6b559

RDX: ffffffffffffffb8 RSI: 00000000200028c0 RDI: 00000000200000c0

RBP: 00007f6117cf0788 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f6117cf0780