Hello,
syzbot found the following issue on:
HEAD commit: e5bbb12db2c7 Linux 6.6.115
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=111dfe7c580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link:
https://syzkaller.appspot.com/bug?extid=89e14cd1d0729829ef10
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/e6860876f0ec/disk-e5bbb12d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/d6c28d7cc7f3/vmlinux-e5bbb12d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/8f52ba3964b2/bzImage-e5bbb12d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+89e14c...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 17559 at fs/inode.c:332 drop_nlink+0xbf/0x100 fs/inode.c:332
Modules linked in:
CPU: 1 PID: 17559 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:drop_nlink+0xbf/0x100 fs/inode.c:332
Code: 48 8b 1b 48 8d bb 78 07 00 00 be 08 00 00 00 e8 57 58 ea ff f0 48 ff 83 78 07 00 00 5b 41 5c 41 5e 41 5f 5d c3 e8 81 fc 92 ff <0f> 0b eb 88 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 62 ff ff ff 4c
RSP: 0018:ffffc900032a7990 EFLAGS: 00010293
RAX: ffffffff81f2930f RBX: ffff888071e68878 RCX: ffff88802cbc1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff90da85a7 R09: 1ffffffff21b50b4
R10: dffffc0000000000 R11: fffffbfff21b50b5 R12: 1ffff1100e3cd11a
R13: 1ffff92000654f48 R14: ffff888071e688d0 R15: dffffc0000000000
FS: 000055557a428500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fae08a99286 CR3: 0000000062fe4000 CR4: 00000000003506e0
Call Trace:
<TASK>
ocfs2_unlink+0x1131/0x18f0 fs/ocfs2/namei.c:1004
vfs_rmdir+0x370/0x4d0 fs/namei.c:4204
do_rmdir+0x29e/0x5c0 fs/namei.c:4263
__do_sys_unlinkat fs/namei.c:4441 [inline]
__se_sys_unlinkat fs/namei.c:4435 [inline]
__x64_sys_unlinkat+0xc4/0xe0 fs/namei.c:4435
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe79db8e5a7
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 07 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdc2ace008 EFLAGS: 00000207 ORIG_RAX: 0000000000000107
RAX: ffffffffffffffda RBX: 0000000000000065 RCX: 00007fe79db8e5a7
RDX: 0000000000000200 RSI: 00007ffdc2acf1b0 RDI: 00000000ffffff9c
RBP: 00007fe79dc11d7d R08: 000055557a44b66b R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000207 R12: 00007ffdc2acf1b0
R13: 00007fe79dc11d7d R14: 000000000016849c R15: 00007ffdc2ad1370
</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 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