From: syzbot <syzbot+9d014e6e0df70d97c103@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, n.zhandarovich@fintech.ru,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] BUG: unable to handle kernel NULL pointer dereference in unlock_page (2)
Date: Thu, 26 Oct 2023 22:11:04 -0700 [thread overview]
Message-ID: <00000000000019b7280608abb7f8@google.com> (raw)
In-Reply-To: <000000000000f3aeec05f025c6b8@google.com>
syzbot suspects this issue was fixed by commit:
commit 013ff63b649475f0ee134e2c8d0c8e65284ede50
Author: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Date: Fri Jun 30 12:17:02 2023 +0000
fs/ntfs3: Add more attributes checks in mi_enum_attr()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10677ddb680000
start commit: 18940c888c85 Merge tag 'sched_urgent_for_v6.3_rc4' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=acdb62bf488a8fe5
dashboard link: https://syzkaller.appspot.com/bug?extid=9d014e6e0df70d97c103
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bf0adec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1391fcd5c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs/ntfs3: Add more attributes checks in mi_enum_attr()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2023-10-27 5:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000f3aeec05f025c6b8@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=00000000000019b7280608abb7f8@google.com \
--to=syzbot+9d014e6e0df70d97c103@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n.zhandarovich@fintech.ru \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).