All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3e5130844b0c0e2b4948@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,  postmaster@duagon.onmicrosoft.com,
	rpeterso@redhat.com,  syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [gfs2?] WARNING: suspicious RCU usage in gfs2_permission
Date: Fri, 20 Oct 2023 00:10:38 -0700	[thread overview]
Message-ID: <000000000000c92c0d06082091ee@google.com> (raw)
In-Reply-To: <0000000000000c44b0060760bd00@google.com>

syzbot has bisected this issue to:

commit 0abd1557e21c617bd13fc18f7725fc6363c05913
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Mon Oct 2 02:33:44 2023 +0000

    gfs2: fix an oops in gfs2_permission

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=10b21c33680000
start commit:   2dac75696c6d Add linux-next specific files for 20231018
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=12b21c33680000
console output: https://syzkaller.appspot.com/x/log.txt?x=14b21c33680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6f8545e1ef7a2b66
dashboard link: https://syzkaller.appspot.com/bug?extid=3e5130844b0c0e2b4948
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=101c8d09680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11a07475680000

Reported-by: syzbot+3e5130844b0c0e2b4948@syzkaller.appspotmail.com
Fixes: 0abd1557e21c ("gfs2: fix an oops in gfs2_permission")

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

  parent reply	other threads:[~2023-10-20  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 18:18 [syzbot] [gfs2?] WARNING: suspicious RCU usage in gfs2_permission syzbot
2023-10-18 14:28 ` syzbot
2023-10-20  7:10 ` syzbot [this message]
2023-10-25  3:21   ` [Cluster-devel] " Al Viro
2023-10-25  3:21     ` Al Viro
2023-10-30 21:05     ` [Cluster-devel] " Andreas Gruenbacher
2023-10-30 21:05       ` Andreas Gruenbacher

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=000000000000c92c0d06082091ee@google.com \
    --to=syzbot+3e5130844b0c0e2b4948@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=postmaster@duagon.onmicrosoft.com \
    --cc=rpeterso@redhat.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.