From: syzbot <syzbot+69d15cab6309bffae739@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
edward.lo@ambergroup.io, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in ni_find_attr
Date: Sun, 05 Feb 2023 11:46:17 -0800 [thread overview]
Message-ID: <00000000000009570005f3f92b86@google.com> (raw)
In-Reply-To: <0000000000009a318805e6ff48a4@google.com>
syzbot suspects this issue was fixed by commit:
commit 2681631c29739509eec59cc0b34e977bb04c6cf1
Author: Edward Lo <edward.lo@ambergroup.io>
Date: Sat Aug 6 17:05:18 2022 +0000
fs/ntfs3: Add null pointer check to attr_load_runs_vcn
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=110ad78d480000
start commit: b7b275e60bcd Linux 6.1-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2325e409a9a893e1
dashboard link: https://syzkaller.appspot.com/bug?extid=69d15cab6309bffae739
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b3fb9b880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101313bb880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Add null pointer check to attr_load_runs_vcn
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-02-05 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000009a318805e6ff48a4@google.com>
2022-08-29 23:30 ` [syzbot] BUG: unable to handle kernel NULL pointer dereference in ni_find_attr syzbot
2023-02-05 19:46 ` syzbot [this message]
2023-02-06 10:20 ` [syzbot] [ntfs3?] " Aleksandr Nogikh
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=00000000000009570005f3f92b86@google.com \
--to=syzbot+69d15cab6309bffae739@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=edward.lo@ambergroup.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).