From: syzbot <syzbot+74edb1a3ea8f1c65a086@syzkaller.appspotmail.com>
To: agruenba@redhat.com, cluster-devel@redhat.com,
gfs2@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] general protection fault in gfs2_rindex_update
Date: Thu, 08 Feb 2024 06:57:09 -0800 [thread overview]
Message-ID: <0000000000009263050610e00681@google.com> (raw)
In-Reply-To: <0000000000001e48350610dbc5c5@google.com>
syzbot has bisected this issue to:
commit de3f906f0af0c3f5d862b07df4d020c9322cd9c3
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date: Thu Jun 2 20:15:02 2022 +0000
gfs2: Revert 'Fix "truncate in progress" hang'
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f06904180000
start commit: 547ab8fc4cb0 Merge tag 'loongarch-fixes-6.8-2' of git://gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17f06904180000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f06904180000
kernel config: https://syzkaller.appspot.com/x/.config?x=89a5d896b14c4565
dashboard link: https://syzkaller.appspot.com/bug?extid=74edb1a3ea8f1c65a086
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11395147e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126ff68fe80000
Reported-by: syzbot+74edb1a3ea8f1c65a086@syzkaller.appspotmail.com
Fixes: de3f906f0af0 ("gfs2: Revert 'Fix "truncate in progress" hang'")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-02-08 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 9:52 [syzbot] [gfs2?] general protection fault in gfs2_rindex_update syzbot
2024-02-08 9:57 ` syzbot
2024-02-09 16:10 ` Andrew Price
2024-02-08 14:57 ` 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=0000000000009263050610e00681@google.com \
--to=syzbot+74edb1a3ea8f1c65a086@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--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