From: syzbot <syzbot+b0373017f711c06ada64@syzkaller.appspotmail.com>
To: kapoorarnav43@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in ni_rename
Date: Mon, 30 Jun 2025 04:55:04 -0700 [thread overview]
Message-ID: <68627b18.a70a0220.3b7e22.0dcc.GAE@google.com> (raw)
In-Reply-To: <0620687c-30d7-405d-b4f3-636546ef1823n@googlegroups.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in ni_rename
loop0: detected capacity change from 0 to 4096
------------[ cut here ]------------
WARNING: fs/ntfs3/frecord.c:3030 at ni_rename+0xee/0x100 fs/ntfs3/frecord.c:3029, CPU#0: syz.0.16/6714
Modules linked in:
CPU: 0 UID: 0 PID: 6714 Comm: syz.0.16 Not tainted 6.16.0-rc4-next-20250630-syzkaller-g1343433ed389 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ni_rename+0xee/0x100 fs/ntfs3/frecord.c:3029
Code: 8b 05 66 63 9a 0f 48 3b 44 24 10 75 22 44 89 e0 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d e9 49 ac 6c 08 cc e8 b3 fe b9 fe 90 <0f> 0b 90 eb c5 e8 18 d2 69 08 0f 1f 84 00 00 00 00 00 90 90 90 90
RSP: 0018:ffffc90002eb7ab8 EFLAGS: 00010293
RAX: ffffffff8305ccdd RBX: 00000000fffffffe RCX: ffff888020b28000
RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 0000000000000000
RBP: 00000000fffffffe R08: ffffffff8fa17437 R09: 1ffffffff1f42e86
R10: dffffc0000000000 R11: fffffbfff1f42e87 R12: 0000000000000000
R13: ffff88803385e600 R14: ffff888077140758 R15: ffff888066ebe6d0
FS: 00007f59ac0016c0(0000) GS:ffff888125c1d000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8e813c3000 CR3: 000000007f64a000 CR4: 00000000003526f0
Call Trace:
<TASK>
ntfs_rename+0x6e2/0xb40 fs/ntfs3/namei.c:316
vfs_rename+0xbd7/0xf00 fs/namei.c:5129
do_renameat2+0x6ce/0xa80 fs/namei.c:5278
__do_sys_rename fs/namei.c:5325 [inline]
__se_sys_rename fs/namei.c:5323 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5323
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f59ab18e929
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:00007f59ac001038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f59ab3b5fa0 RCX: 00007f59ab18e929
RDX: 0000000000000000 RSI: 0000200000001040 RDI: 0000200000000280
RBP: 00007f59ab210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f59ab3b5fa0 R15: 00007fff104b3398
</TASK>
Tested on:
commit: 1343433e Add linux-next specific files for 20250630
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10bfa770580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c1ce97baf6bd6397
dashboard link: https://syzkaller.appspot.com/bug?extid=b0373017f711c06ada64
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=1147848c580000
next parent reply other threads:[~2025-06-30 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0620687c-30d7-405d-b4f3-636546ef1823n@googlegroups.com>
2025-06-30 11:55 ` syzbot [this message]
2025-07-08 21:45 [syzbot] [ntfs3?] WARNING in ni_rename Moon Hee Lee
2025-07-08 22:11 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 8:39 Moon Hee Lee
2025-07-08 9:06 ` syzbot
2025-07-08 7:54 Moonhee Lee
2025-07-08 8:13 ` syzbot
2025-07-08 8:21 ` Moon Hee Lee
2025-07-08 8:38 ` syzbot
[not found] <8b0a6266-d5c9-43e0-994d-df557fbf8f0fn@googlegroups.com>
2025-06-30 23:50 ` syzbot
[not found] <e4eb2024-f891-4548-ac08-4f224877c902n@googlegroups.com>
2025-06-30 23:45 ` syzbot
[not found] <840cee6a-44db-4c88-8501-6291f0c26486n@googlegroups.com>
2025-06-30 14:32 ` syzbot
[not found] <e13eff57-579f-4eca-9bc3-9f6ec2d5f42fn@googlegroups.com>
2025-06-30 11:21 ` syzbot
2025-06-29 9:46 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68627b18.a70a0220.3b7e22.0dcc.GAE@google.com \
--to=syzbot+b0373017f711c06ada64@syzkaller.appspotmail.com \
--cc=kapoorarnav43@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.