From: syzbot <syzbot+10c6178a65acf04efe47@syzkaller.appspotmail.com>
To: agruenba@redhat.com, cluster-devel@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
rpeterso@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: sleeping function called from invalid context in glock_hash_walk
Date: Wed, 06 Sep 2023 01:46:34 -0700 [thread overview]
Message-ID: <000000000000de54840604acc740@google.com> (raw)
In-Reply-To: <00000000000057049306049e0525@google.com>
syzbot has bisected this issue to:
commit 0be8432166a61abc537e1247e530f4b85970b56b
Author: Bob Peterson <rpeterso@redhat.com>
Date: Wed Aug 2 14:24:12 2023 +0000
gfs2: Don't use filemap_splice_read
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1470c620680000
start commit: 3f86ed6ec0b3 Merge tag 'arc-6.6-rc1' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1670c620680000
console output: https://syzkaller.appspot.com/x/log.txt?x=1270c620680000
kernel config: https://syzkaller.appspot.com/x/.config?x=ff0db7a15ba54ead
dashboard link: https://syzkaller.appspot.com/bug?extid=10c6178a65acf04efe47
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e4ea14680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f76f10680000
Reported-by: syzbot+10c6178a65acf04efe47@syzkaller.appspotmail.com
Fixes: 0be8432166a6 ("gfs2: Don't use filemap_splice_read")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-06 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 15:10 [syzbot] [gfs2?] BUG: sleeping function called from invalid context in glock_hash_walk syzbot
2023-09-06 8:46 ` syzbot [this message]
2024-01-16 3:35 ` syzbot
2024-01-16 10:33 ` Jan Kara
2024-01-16 15:55 ` 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=000000000000de54840604acc740@google.com \
--to=syzbot+10c6178a65acf04efe47@syzkaller.appspotmail.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).