From: syzbot <syzbot+deb631beeb93bdb2df4c@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
nathan@kernel.org, ndesaulniers@google.com,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
trix@redhat.com
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in ntfs_sparse_cluster
Date: Tue, 31 Jan 2023 15:05:17 -0800 [thread overview]
Message-ID: <0000000000007dd57305f3975d7d@google.com> (raw)
In-Reply-To: <00000000000010d44905f01bf8e7@google.com>
syzbot suspects this issue was fixed by commit:
commit c380b52f6c5702cc4bdda5e6d456d6c19a201a0b
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Oct 7 11:02:36 2022 +0000
fs/ntfs3: Change new sparse cluster processing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1377b979480000
start commit: e2ca6ba6ba01 Merge tag 'mm-stable-2022-12-13' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=276eb8ff64eb2c27
dashboard link: https://syzkaller.appspot.com/bug?extid=deb631beeb93bdb2df4c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d8601b880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a09c93880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Change new sparse cluster processing
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-31 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 15:36 [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in ntfs_sparse_cluster syzbot
2023-01-31 23:05 ` syzbot [this message]
2023-02-01 8:12 ` Dmitry Vyukov
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=0000000000007dd57305f3975d7d@google.com \
--to=syzbot+deb631beeb93bdb2df4c@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trix@redhat.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;
as well as URLs for NNTP newsgroup(s).