From: syzbot <syzbot+4d8e30dbafb5c1260479@syzkaller.appspotmail.com>
To: kshitijvparanjape@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in ni_rename (2)
Date: Mon, 10 Nov 2025 09:18:02 -0800 [thread overview]
Message-ID: <69121e4a.a70a0220.22f260.00f9.GAE@google.com> (raw)
In-Reply-To: <CAJ9gUkHct+WE_cZN48BcNRuvcVnwf+qeOFxMCF+t263KqZAetg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4d8e30dbafb5c1260479@syzkaller.appspotmail.com
Tested-by: syzbot+4d8e30dbafb5c1260479@syzkaller.appspotmail.com
Tested on:
commit: e9a6fb0b Linux 6.18-rc5
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11508c12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=4d8e30dbafb5c1260479
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=174ab412580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-10 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ9gUkHct+WE_cZN48BcNRuvcVnwf+qeOFxMCF+t263KqZAetg@mail.gmail.com>
2025-11-10 17:18 ` syzbot [this message]
[not found] <20260319163058.304780-1-junjie.cao@linux.dev>
2026-03-19 19:50 ` syzbot
[not found] <20260319154838.293419-1-junjie.cao@linux.dev>
2026-03-19 16:04 ` syzbot
[not found] <20260319153911.289905-1-junjie.cao@linux.dev>
2026-03-19 15:50 ` syzbot
[not found] <20260319112858.213422-1-junjie.cao@linux.dev>
2026-03-19 14:05 ` syzbot
[not found] <kj6hgbdwsmff55vzjvmlsvybcmhrdywa2d4fxqt7376ocmocle@5jrydocarqf2>
2025-11-04 7:03 ` syzbot
[not found] <uzq2pgc3ufm7iewqzhfnujt5pwqcsadnfgufywp5gx6guzdtye@4pxj7vqewujt>
2025-11-04 6:34 ` syzbot
2025-10-30 22:35 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=69121e4a.a70a0220.22f260.00f9.GAE@google.com \
--to=syzbot+4d8e30dbafb5c1260479@syzkaller.appspotmail.com \
--cc=kshitijvparanjape@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®