From: syzbot <syzbot+b892240eac461e488d51@syzkaller.appspotmail.com>
To: abdun.nihaal@gmail.com, almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
skhan@linuxfoundation.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] KASAN: slab-out-of-bounds Read in ntfs_trim_fs
Date: Sun, 02 Oct 2022 13:04:19 -0700 [thread overview]
Message-ID: <0000000000007ae43605ea12bb12@google.com> (raw)
In-Reply-To: <000000000000eca83705e9a72fb9@google.com>
syzbot has bisected this issue to:
commit 6e5be40d32fb1907285277c02e74493ed43d77fe
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Aug 13 14:21:30 2021 +0000
fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b6daf4880000
start commit: f76349cf4145 Linux 6.0-rc7
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1476daf4880000
console output: https://syzkaller.appspot.com/x/log.txt?x=1076daf4880000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba0d23aa7e1ffaf5
dashboard link: https://syzkaller.appspot.com/bug?extid=b892240eac461e488d51
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=133c8540880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11b74870880000
Reported-by: syzbot+b892240eac461e488d51@syzkaller.appspotmail.com
Fixes: 6e5be40d32fb ("fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-10-02 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 11:45 [syzbot] KASAN: slab-out-of-bounds Read in ntfs_trim_fs syzbot
2022-10-02 20:04 ` syzbot [this message]
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=0000000000007ae43605ea12bb12@google.com \
--to=syzbot+b892240eac461e488d51@syzkaller.appspotmail.com \
--cc=abdun.nihaal@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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