From: syzbot <syzbot+ef50f8eb00b54feb7ba2@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, anton@tuxera.com,
brauner@kernel.org, david@fromorbit.com, ghandatmanas@gmail.com,
linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, syzkaller@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [ntfs3?] KASAN: use-after-free Read in ntfs_attr_find (2)
Date: Tue, 19 Mar 2024 04:03:03 -0700 [thread overview]
Message-ID: <0000000000000a1c180614016bc9@google.com> (raw)
In-Reply-To: <000000000000aefc5005f5df169b@google.com>
syzbot suspects this issue was fixed by commit:
commit 7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Mon Jan 15 07:20:25 2024 +0000
fs: Remove NTFS classic
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11fafac9180000
start commit: 9d64bf433c53 Merge tag 'perf-tools-for-v6.8-1-2024-01-09' ..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7a6ff9d9d5d2dc4a
dashboard link: https://syzkaller.appspot.com/bug?extid=ef50f8eb00b54feb7ba2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13d79fbde80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14be4a73e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Remove NTFS classic
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2024-03-19 11:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000aefc5005f5df169b@google.com>]
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=0000000000000a1c180614016bc9@google.com \
--to=syzbot+ef50f8eb00b54feb7ba2@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=anton@tuxera.com \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=ghandatmanas@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).