From: syzbot <syzbot+af224b63e76b2d869bc3@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org,
almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
neilb@suse.de, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: [syzbot] [ntfs3?] general protection fault in ni_readpage_cmpr
Date: Sun, 11 Jun 2023 15:17:27 -0700 [thread overview]
Message-ID: <000000000000a0c29605fde1f706@google.com> (raw)
In-Reply-To: <000000000000b0cabf05f90bcb15@google.com>
syzbot has bisected this issue to:
commit 9fd472af84abd6da15376353c2283b3df9497646
Author: NeilBrown <neilb@suse.de>
Date: Tue Mar 22 21:38:54 2022 +0000
mm: improve cleanup when ->readpages doesn't process all pages
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1285d453280000
start commit: 64569520920a Merge tag 'block-6.4-2023-06-09' of git://git..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1185d453280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1685d453280000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c980bfe8b399968
dashboard link: https://syzkaller.appspot.com/bug?extid=af224b63e76b2d869bc3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15835795280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16966d43280000
Reported-by: syzbot+af224b63e76b2d869bc3@syzkaller.appspotmail.com
Fixes: 9fd472af84ab ("mm: improve cleanup when ->readpages doesn't process all pages")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-11 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 9:05 [syzbot] [ntfs3?] general protection fault in ni_readpage_cmpr syzbot
2023-05-07 10:30 ` syzbot
2023-06-11 22:17 ` syzbot [this message]
2023-11-21 15:58 ` syzbot
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=000000000000a0c29605fde1f706@google.com \
--to=syzbot+af224b63e76b2d869bc3@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=neilb@suse.de \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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