From: syzbot <syzbot+2e6c1eda2eff0745b028@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, anmuxixixi@gmail.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in ntfs_fill_super (2)
Date: Wed, 29 Oct 2025 16:47:03 -0700 [thread overview]
Message-ID: <6902a777.a70a0220.5b2ed.0015.GAE@google.com> (raw)
In-Reply-To: <69015bf1.050a0220.3344a1.03f8.GAE@google.com>
syzbot has bisected this issue to:
commit 02f312754c873efe076888a2fdca982e56617929
Author: YangWen <anmuxixixi@gmail.com>
Date: Wed Sep 10 15:17:08 2025 +0000
ntfs3: fix use-after-free of sbi->options in cmp_fnames
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11825f34580000
start commit: f7d2388eeec2 Add linux-next specific files for 20251028
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=13825f34580000
console output: https://syzkaller.appspot.com/x/log.txt?x=15825f34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ecdce5bceba74f
dashboard link: https://syzkaller.appspot.com/bug?extid=2e6c1eda2eff0745b028
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116e6704580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11198fe2580000
Reported-by: syzbot+2e6c1eda2eff0745b028@syzkaller.appspotmail.com
Fixes: 02f312754c87 ("ntfs3: fix use-after-free of sbi->options in cmp_fnames")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-29 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 0:12 [syzbot] [ntfs3?] WARNING in ntfs_fill_super (2) syzbot
2025-10-29 23:47 ` syzbot [this message]
2025-11-02 16:40 ` Forwarded: syzbot
2025-11-03 13:28 ` Forwarded: syzbot
[not found] <589113983.3481676.1762101635409@kpc.webmail.kpnmail.nl>
2025-11-02 17:07 ` [syzbot] [ntfs3?] WARNING in ntfs_fill_super (2) 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=6902a777.a70a0220.5b2ed.0015.GAE@google.com \
--to=syzbot+2e6c1eda2eff0745b028@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=anmuxixixi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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