From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+4fcffdd85e518af6f129@syzkaller.appspotmail.com>
Cc: agruenba@redhat.com, akpm@linux-foundation.org,
anprice@redhat.com, axboe@kernel.dk, brauner@kernel.org,
cluster-devel@redhat.com, dvyukov@google.com, elver@google.com,
gfs2@lists.linux.dev, glider@google.com, jack@suse.cz,
kasan-dev@googlegroups.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] INFO: task hung in write_cache_pages (3)
Date: Fri, 16 Feb 2024 12:43:32 +0100 [thread overview]
Message-ID: <20240216114332.syzemwegji72j4uh@quack3> (raw)
In-Reply-To: <000000000000b06c9e06117db32b@google.com>
On Fri 16-02-24 03:04:03, 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=151b2b78180000
> start commit: 92901222f83d Merge tag 'f2fs-for-6-6-rc1' of git://git.ker..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3d78b3780d210e21
> dashboard link: https://syzkaller.appspot.com/bug?extid=4fcffdd85e518af6f129
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17933a00680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ef7104680000
>
> 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
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-02-16 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 7:28 syzbot
[not found] ` <000000000000b06c9e06117db32b@google.com>
2024-02-16 11:43 ` Jan Kara [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=20240216114332.syzemwegji72j4uh@quack3 \
--to=jack@suse.cz \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anprice@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cluster-devel@redhat.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gfs2@lists.linux.dev \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+4fcffdd85e518af6f129@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