From: syzbot <syzbot+6b156e132970e550194c@syzkaller.appspotmail.com>
To: agruenba@redhat.com, eadavis@qq.com, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] general protection fault in gfs2_log_is_empty
Date: Wed, 15 Oct 2025 06:47:04 -0700 [thread overview]
Message-ID: <68efa5d8.050a0220.91a22.0263.GAE@google.com> (raw)
In-Reply-To: <68ef030a.050a0220.91a22.022a.GAE@google.com>
syzbot has bisected this issue to:
commit 578194d38a129a7b60ddd90d226ea517605db30d
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date: Thu Jul 31 21:49:37 2025 +0000
Revert "gfs2: Force withdraw to replay journals and wait for it to finish" (6/6)
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10df95e2580000
start commit: 52ba76324a9d Add linux-next specific files for 20251013
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=12df95e2580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14df95e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=99cb6b007a8889ef
dashboard link: https://syzkaller.appspot.com/bug?extid=6b156e132970e550194c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132af304580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cd7892580000
Reported-by: syzbot+6b156e132970e550194c@syzkaller.appspotmail.com
Fixes: 578194d38a12 ("Revert "gfs2: Force withdraw to replay journals and wait for it to finish" (6/6)")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-10-15 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 2:12 [syzbot] [gfs2?] general protection fault in gfs2_log_is_empty syzbot
2025-10-15 9:51 ` [PATCH next] gfs2: Add sanity check for sd_jdesc Edward Adam Davis
2025-10-15 9:59 ` [PATCH next V2] " Edward Adam Davis
2025-10-16 16:43 ` [PATCH next] " Andreas Gruenbacher
2025-10-15 13:47 ` syzbot [this message]
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=68efa5d8.050a0220.91a22.0263.GAE@google.com \
--to=syzbot+6b156e132970e550194c@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=eadavis@qq.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--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