Hello,
syzbot found the following issue on:
HEAD commit: 1e89a1be4fe9 Linux 6.6.117
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17ec7e92580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link:
https://syzkaller.appspot.com/bug?extid=8210de6a6e62bb151aa1
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/ad3647e47b66/disk-1e89a1be.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/d6f7ba94aea7/vmlinux-1e89a1be.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e08af2290355/bzImage-1e89a1be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8210de...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 11534 at fs/ntfs3/frecord.c:3085 ni_rename+0xea/0x100 fs/ntfs3/frecord.c:3084
Modules linked in:
CPU: 0 PID: 11534 Comm: syz.4.1162 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ni_rename+0xea/0x100 fs/ntfs3/frecord.c:3084
Code: 5a bf fe 65 48 8b 04 25 28 00 00 00 48 3b 44 24 10 75 1b 44 89 e0 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f6 59 bf fe <0f> 0b eb cb e8 1d f6 a8 07 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00
RSP: 0018:ffffc90005277af8 EFLAGS: 00010283
RAX: ffffffff82c6468a RBX: 00000000fffffffe RCX: 0000000000080000
RDX: ffffc9001a000000 RSI: 000000000000403f RDI: 0000000000004040
RBP: 00000000fffffffe R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000020 R11: 0000000000000002 R12: 0000000000000000
R13: ffff888059210000 R14: ffff8880440b0760 R15: ffff8880440b0ec0
FS: 00007f1ca91576c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055557e05b608 CR3: 00000000678b0000 CR4: 00000000003506f0
Call Trace:
<TASK>
ntfs_rename+0x6dc/0xb30 fs/ntfs3/namei.c:333
vfs_rename+0xb96/0xec0 fs/namei.c:4880
do_renameat2+0x8a1/0xc70 fs/namei.c:5033
__do_sys_rename fs/namei.c:5079 [inline]
__se_sys_rename fs/namei.c:5077 [inline]
__x64_sys_rename+0x86/0x90 fs/namei.c:5077
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:0x7f1ca838f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1ca9157038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f1ca85e5fa0 RCX: 00007f1ca838f749
RDX: 0000000000000000 RSI: 0000200000000440 RDI: 0000200000000340
RBP: 00007f1ca8413f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1ca85e6038 R14: 00007f1ca85e5fa0 R15: 00007ffed829a0e8
</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