From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+47c7e14e1bd09234d0ad@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, axboe@kernel.dk, brauner@kernel.org,
jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [mm] [fs] possible deadlock in page_cache_ra_unbounded
Date: Fri, 21 Feb 2025 15:56:32 +0100 [thread overview]
Message-ID: <y5kibif4m6shs4c44o6c46mhi6mengffft2rfnnjk4djtxiqbb@bxbhd6rx6uof> (raw)
In-Reply-To: <67b75632.050a0220.14d86d.02e4.GAE@google.com>
On Thu 20-02-25 08:20:02, 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=16e867f8580000
> start commit: 861deac3b092 Linux 6.7-rc7
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e1e118a9228c45d7
> dashboard link: https://syzkaller.appspot.com/bug?extid=47c7e14e1bd09234d0ad
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=100b9595e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1415ff9ee80000
>
> 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:[~2025-02-21 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 8:15 [syzbot] " syzbot
2023-06-26 23:27 ` [syzbot] [reiserfs?] " syzbot
2025-02-20 16:20 ` [syzbot] [mm] [fs] " syzbot
2025-02-21 14:56 ` 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=y5kibif4m6shs4c44o6c46mhi6mengffft2rfnnjk4djtxiqbb@bxbhd6rx6uof \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzbot+47c7e14e1bd09234d0ad@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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