[v6.1] WARNING in ocfs2_unlink

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 04d1ccaa9c28 Linux 6.1.143
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1244df70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=30fae84d50729cf
dashboard link: https://syzkaller.appspot.com/bug?extid=4f5e1fb963d07d760bfd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6be65a5e6fec/disk-04d1ccaa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/52fda42cf9c4/vmlinux-04d1ccaa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0491d42b7947/Image-04d1ccaa.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5993 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 0 PID: 5993 Comm: syz-executor Not tainted 6.1.143-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
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 : ffff800020e277e0
x29: ffff800020e277e0 x28: 1fffe0001ebfb49f x27: ffff0000f5f0c178
x26: ffff0000f5f0c178 x25: ffff7000041c4f10 x24: 00000000000000b3
x23: 1fffe0001ebe1838 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000f5f0c1c0 x19: ffff0000f5f0c178 x18: ffff800011aabce0
x17: ffff8000181e6000 x16: ffff8000082d2400 x15: ffff800017cc6fc0
x14: ffff0000daee5dd8 x13: 00000000173eed80 x12: 0000000000ff0100
x11: ff008000089fb9e4 x10: 0000000000000000 x9 : ffff8000089fb9e4
x8 : ffff0000daee5340 x7 : 00000000173eed80 x6 : 00000000000000b3
x5 : ffff0000f5f0c200 x4 : ffff0000f5f0c1f0 x3 : ffff800009d6bc48
x2 : 0000000000000010 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
ocfs2_unlink+0xce4/0x15e4 fs/ocfs2/namei.c:1002
vfs_rmdir+0x304/0x438 fs/namei.c:4191
do_rmdir+0x238/0x50c fs/namei.c:4252
__do_sys_unlinkat fs/namei.c:4432 [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/0x138 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: 787262
hardirqs last enabled at (787261): [<ffff8000083bf614>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (787261): [<ffff8000083bf614>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (787262): [<ffff800011943868>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (787222): [<ffff8000081a9670>] softirq_handle_end kernel/softirq.c:439 [inline]
softirqs last enabled at (787222): [<ffff8000081a9670>] handle_softirqs+0xaf8/0xc6c kernel/softirq.c:624
softirqs last disabled at (787207): [<ffff800008020164>] __do_softirq+0x14/0x20 kernel/softirq.c:630
---[ end trace 0000000000000000 ]---
ocfs2: Unmounting device (7,5) on (node local)


---
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: 04d1ccaa9c28 Linux 6.1.143
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=112adf70580000

kernel config: https://syzkaller.appspot.com/x/.config?x=30fae84d50729cf
dashboard link: https://syzkaller.appspot.com/bug?extid=4f5e1fb963d07d760bfd
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b5c28c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=110e5582580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6be65a5e6fec/disk-04d1ccaa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/52fda42cf9c4/vmlinux-04d1ccaa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0491d42b7947/Image-04d1ccaa.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/db46b5887239/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1735c28c580000)

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

------------[ cut here ]------------

WARNING: CPU: 1 PID: 4410 at fs/inode.c:332 drop_nlink+0xe4/0x138 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 4410 Comm: syz-executor Not tainted 6.1.143-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
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 : ffff800020f177e0
x29: ffff800020f177e0 x28: 1fffe0001d120bbf x27: ffff0000e8bb8878
x26: ffff0000e8bb8878 x25: ffff7000041e2f10 x24: 0000000000000042
x23: 1fffe0001d177118 x22: dfff800000000000 x21: 0000000000000000
x20: ffff0000e8bb88c0 x19: ffff0000e8bb8878 x18: 0000000000000000

x17: ffff8000181e6000 x16: ffff8000082d2400 x15: ffff800017cc6fc0

x14: ffff0000da350a98 x13: 00000000350c5280 x12: 0000000000ff0100

x11: ff008000089fb9e4 x10: 0000000000000000 x9 : ffff8000089fb9e4

x8 : ffff0000da350000 x7 : 00000000350c5280 x6 : 0000000000000042
x5 : ffff0000e8bb8900 x4 : ffff0000e8bb88f0 x3 : ffff800009d6bc48

x2 : 0000000000000010 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
drop_nlink+0xe4/0x138 fs/inode.c:332
ocfs2_unlink+0xce4/0x15e4 fs/ocfs2/namei.c:1002
vfs_rmdir+0x304/0x438 fs/namei.c:4191
do_rmdir+0x238/0x50c fs/namei.c:4252
__do_sys_unlinkat fs/namei.c:4432 [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/0x138 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: 160634
hardirqs last enabled at (160633): [<ffff8000083bf614>] seqcount_lockdep_reader_access include/linux/seqlock.h:104 [inline]
hardirqs last enabled at (160633): [<ffff8000083bf614>] ktime_get_coarse_real_ts64+0x114/0x244 kernel/time/timekeeping.c:2261
hardirqs last disabled at (160634): [<ffff800011943868>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (160366): [<ffff800008030900>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (160364): [<ffff8000080308cc>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19

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