From: syzbot <syzbot+50a8a9cf8127f2c6f5df@syzkaller.appspotmail.com>
To: agruenba@redhat.com, anprice@redhat.com,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
rpeterso@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in gfs2_withdraw
Date: Mon, 28 Sep 2020 22:34:06 -0700 [thread overview]
Message-ID: <000000000000a7770405b06d21ac@google.com> (raw)
In-Reply-To: <000000000000b6d7fd05b02037ef@google.com>
syzbot has bisected this issue to:
commit 601ef0d52e9617588fcff3df26953592f2eb44ac
Author: Bob Peterson <rpeterso@redhat.com>
Date: Tue Jan 28 19:23:45 2020 +0000
gfs2: Force withdraw to replay journals and wait for it to finish
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=151d25e3900000
start commit: 7c7ec322 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=171d25e3900000
console output: https://syzkaller.appspot.com/x/log.txt?x=131d25e3900000
kernel config: https://syzkaller.appspot.com/x/.config?x=6184b75aa6d48d66
dashboard link: https://syzkaller.appspot.com/bug?extid=50a8a9cf8127f2c6f5df
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c6a109900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15d45ed3900000
Reported-by: syzbot+50a8a9cf8127f2c6f5df@syzkaller.appspotmail.com
Fixes: 601ef0d52e96 ("gfs2: Force withdraw to replay journals and wait for it to finish")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-09-29 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:48 general protection fault in gfs2_withdraw syzbot
2020-09-26 17:21 ` syzbot
2020-09-28 13:39 ` [Cluster-devel] " Andrew Price
2020-09-28 13:52 ` Bob Peterson
2020-09-29 5:34 ` syzbot [this message]
2020-09-30 14:18 ` Andrew Price
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=000000000000a7770405b06d21ac@google.com \
--to=syzbot+50a8a9cf8127f2c6f5df@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=anprice@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--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 NNTP newsgroup(s).