cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com>
Cc: elver@google.com, peterz@infradead.org,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	cluster-devel@redhat.com, linux-fsdevel@vger.kernel.org,
	valentin.schneider@arm.com
Subject: Re: [Cluster-devel] [syzbot] [gfs2?] general protection fault in gfs2_dump_glock (2)
Date: Tue, 5 Sep 2023 11:57:20 +0200	[thread overview]
Message-ID: <CANp29Y4nitnu-iF77=8rNH_k02=N_1+C7C-ix_1XmpMsf1A=BA@mail.gmail.com> (raw)
In-Reply-To: <000000000000fe1297060492eb88@google.com>

Hmm, no, it might theoretically be that preemption affected bug
reproducibility, but this commit itself definitely has nothing to do
with the gfs2 problem.

On Tue, Sep 5, 2023 at 3:55 AM syzbot
<syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this issue to:
>
> commit a8b76910e465d718effce0cad306a21fa4f3526b
> Author: Valentin Schneider <valentin.schneider@arm.com>
> Date:   Wed Nov 10 20:24:44 2021 +0000
>
>     preempt: Restore preemption model selection configs
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1633aaf0680000
> start commit:   58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k..
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=1533aaf0680000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1133aaf0680000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89
> dashboard link: https://syzkaller.appspot.com/bug?extid=427fed3295e9a7e887f2
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=172bead8280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14d01d08280000
>
> Reported-by: syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com
> Fixes: a8b76910e465 ("preempt: Restore preemption model selection configs")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>


      reply	other threads:[~2023-09-05  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 17:44 [Cluster-devel] [syzbot] [cluster?] general protection fault in gfs2_dump_glock (2) syzbot
2023-09-05  1:55 ` [Cluster-devel] [syzbot] [gfs2?] " syzbot
2023-09-05  9:57   ` Aleksandr Nogikh [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='CANp29Y4nitnu-iF77=8rNH_k02=N_1+C7C-ix_1XmpMsf1A=BA@mail.gmail.com' \
    --to=nogikh@google.com \
    --cc=cluster-devel@redhat.com \
    --cc=elver@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=syzbot+427fed3295e9a7e887f2@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=valentin.schneider@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).