From: syzbot <syzbot+dbbd022e608bb122cf4e@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [syzbot] general protection fault in do_mpage_readpage
Date: Sat, 25 Jun 2022 06:29:07 -0700 [thread overview]
Message-ID: <000000000000da315705e245abfa@google.com> (raw)
In-Reply-To: <00000000000073aa8605e1df6ab9@google.com>
syzbot has bisected this issue to:
commit 4c27dc762d7b60fa23c6eab2309ca6fc625588dd
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Sat Jun 11 02:58:24 2022 +0000
mpage: Convert do_mpage_readpage() to use a folio
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16d2a888080000
start commit: 34d1d36073ea Add linux-next specific files for 20220621
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15d2a888080000
console output: https://syzkaller.appspot.com/x/log.txt?x=11d2a888080000
kernel config: https://syzkaller.appspot.com/x/.config?x=b24b62d1c051cfc8
dashboard link: https://syzkaller.appspot.com/bug?extid=dbbd022e608bb122cf4e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1216c174080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14362fd8080000
Reported-by: syzbot+dbbd022e608bb122cf4e@syzkaller.appspotmail.com
Fixes: 4c27dc762d7b ("mpage: Convert do_mpage_readpage() to use a folio")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-25 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 11:29 [syzbot] general protection fault in do_mpage_readpage syzbot
2022-06-21 21:04 ` syzbot
2022-06-25 13:29 ` syzbot [this message]
[not found] <20220623110941.566-1-hdanton@sina.com>
2022-06-23 14:38 ` 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=000000000000da315705e245abfa@google.com \
--to=syzbot+dbbd022e608bb122cf4e@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.