[v6.1] WARNING in minix_unlink

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11f79330580000
kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link: https://syzkaller.appspot.com/bug?extid=56df5be3577930a6838a
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/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz

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

minix_free_block (loop4:21): bit already cleared
minix_free_block (loop4:19): bit already cleared
minix_free_block (loop4:22): bit already cleared
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4296 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 4296 Comm: syz-executor Not tainted 6.1.119-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 : ffff8000216a7a60
x29: ffff8000216a7a60 x28: dfff800000000000 x27: 1fffe0001c27080d
x26: 0000000000000000 x25: 1ffff000042d4f58 x24: 1ffff000042d4f54
x23: 1fffe0001c237965 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e11bcb28 x19: ffff0000e11bcae0 x18: 0000000000000010
x17: 0000000000000000 x16: ffff800012272b80 x15: 0000000000000000
x14: 1ffff00002b500b2 x13: 0000000000000000 x12: 000000000000006b
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008aab0a4
x8 : ffff0000d92ab780 x7 : 0000000000000000 x6 : 000000000000006b
x5 : ffff0000e11bcb68 x4 : ffff0000e11bc0c8 x3 : ffff800008ff6c5c
x2 : 0000000000000010 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
inode_dec_link_count include/linux/fs.h:2582 [inline]
minix_unlink+0x128/0x180 fs/minix/namei.c:167
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: 544598
hardirqs last enabled at (544597): [<ffff800008403650>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (544597): [<ffff800008403650>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (544598): [<ffff800012320d2c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (544418): [<ffff800008030310>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (544416): [<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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 29f02ec58a94 Linux 6.1.121
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15921fe8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f738f3c37768d3ef

dashboard link: https://syzkaller.appspot.com/bug?extid=56df5be3577930a6838a
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=15beef30580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1797c0c4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f0e977ac21f4/disk-29f02ec5.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2114c6ce7c93/vmlinux-29f02ec5.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3ec83a920b74/Image-29f02ec5.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6222ffe6c665/mount_0.gz

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

minix_free_block (loop0:21): bit already cleared
minix_free_block (loop0:22): bit already cleared
minix_free_block (loop0:19): bit already cleared
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4292 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 4292 Comm: syz-executor182 Tainted: G W 6.1.121-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 : ffff800020fc7a60
x29: ffff800020fc7a60 x28: dfff800000000000 x27: 1fffe0001bd874f8
x26: 0000000000000000 x25: 1ffff000041f8f58 x24: 1ffff000041f8f54
x23: 1fffe0001c37d165 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e1be8b28 x19: ffff0000e1be8ae0 x18: 0000000000000010
x17: 0000000000000000 x16: ffff800012279d40 x15: 0000000000000000
x14: 1ffff00002b520b2 x13: 0000000000000000 x12: 0000000000000025
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008aae918
x8 : ffff0000d4a05340 x7 : 0000000000000000 x6 : 0000000000000025
x5 : ffff0000e1be8b68 x4 : ffff0000e1be80c8 x3 : ffff800008ffbe9c

x2 : 0000000000000010 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
inode_dec_link_count include/linux/fs.h:2582 [inline]
minix_unlink+0x128/0x180 fs/minix/namei.c:167
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: 19202
hardirqs last enabled at (19201): [<ffff800008404f44>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (19201): [<ffff800008404f44>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (19202): [<ffff800012327fd4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (18094): [<ffff8000081c3418>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (18094): [<ffff8000081c3418>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (17949): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605

---[ end trace 0000000000000000 ]---


---

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.