From: Andreas Gruenbacher <agruenba@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+10c6178a65acf04efe47@syzkaller.appspotmail.com>,
axboe@kernel.dk, brauner@kernel.org, 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?] BUG: sleeping function called from invalid context in glock_hash_walk
Date: Tue, 16 Jan 2024 16:55:43 +0100 [thread overview]
Message-ID: <CAHc6FU6wzkniuMormDzthUpj3fCap-iFFRfa_skEAvp6fwBOJA@mail.gmail.com> (raw)
In-Reply-To: <20240116103300.bpv233hnhvfk3uvf@quack3>
On Tue, Jan 16, 2024 at 11:33 AM Jan Kara <jack@suse.cz> wrote:
> On Mon 15-01-24 19:35:05, syzbot wrote:
> > syzbot suspects this issue was fixed by commit:
> >
> > commit 6f861765464f43a71462d52026fbddfc858239a5
> > Author: Jan Kara <jack@suse.cz>
> > Date: Wed Nov 1 17:43:10 2023 +0000
> >
> > fs: Block writes to mounted block devices
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=165bebf5e80000
> > start commit: 3f86ed6ec0b3 Merge tag 'arc-6.6-rc1' of git://git.kernel.o..
> > git tree: upstream
> > 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
> >
> > If the result looks correct, please mark the issue as fixed by replying with:
> >
>
> Makes sense.
>
> #syz fix: fs: Block writes to mounted block devices
Thank you, Jan.
Andreas
prev parent reply other threads:[~2024-01-16 15:55 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
2024-01-16 3:35 ` syzbot
2024-01-16 10:33 ` Jan Kara
2024-01-16 15:55 ` Andreas Gruenbacher [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=CAHc6FU6wzkniuMormDzthUpj3fCap-iFFRfa_skEAvp6fwBOJA@mail.gmail.com \
--to=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cluster-devel@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=syzbot+10c6178a65acf04efe47@syzkaller.appspotmail.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).