All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com>
To: agruenba@redhat.com, gfs2@lists.linux.dev, hdanton@sina.com,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: corrupted list in gfs2_fill_super
Date: Sun, 21 Jul 2024 15:11:02 -0700	[thread overview]
Message-ID: <0000000000004485fa061dc93442@google.com> (raw)
In-Reply-To: <0000000000002501960619e2366b@google.com>

syzbot has bisected this issue to:

commit 30e388d573673474cbd089dec83688331c117add
Author: Andreas Gruenbacher <agruenba@redhat.com>
Date:   Thu Apr 11 12:13:30 2024 +0000

    gfs2: Switch to a per-filesystem glock workqueue

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13653eb5980000
start commit:   523b23f0bee3 Add linux-next specific files for 20240710
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=10e53eb5980000
console output: https://syzkaller.appspot.com/x/log.txt?x=17653eb5980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=98dd8c4bab5cdce
dashboard link: https://syzkaller.appspot.com/bug?extid=d34c2a269ed512c531b0
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16907bb9980000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10ce66a5980000

Reported-by: syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com
Fixes: 30e388d57367 ("gfs2: Switch to a per-filesystem glock workqueue")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-07-21 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  6:20 [syzbot] [gfs2?] BUG: corrupted list in gfs2_fill_super syzbot
2024-06-02  9:50 ` Hillf Danton
2024-06-02 10:23   ` syzbot
2024-07-11 11:00 ` syzbot
2024-07-21 22:11 ` 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=0000000000004485fa061dc93442@google.com \
    --to=syzbot+d34c2a269ed512c531b0@syzkaller.appspotmail.com \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --cc=hdanton@sina.com \
    --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 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.