From: Matthew Wilcox <willy@infradead.org>
To: syzbot <syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com>
Cc: asmadeus@codewreck.org, chao@kernel.org, dhowells@redhat.com,
hch@lst.de, hdanton@sina.com, jaegeuk@kernel.org,
jlayton@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
netfs@lists.linux.dev, syzkaller-bugs@googlegroups.com,
v9fs@lists.linux.dev
Subject: Re: [syzbot] [netfs?] kernel BUG in folio_unlock (3)
Date: Sun, 1 Jun 2025 01:26:04 +0100 [thread overview]
Message-ID: <aDueHCMDLPs2UtY2@casper.infradead.org> (raw)
In-Reply-To: <683b8ea2.a00a0220.d8eae.0020.GAE@google.com>
On Sat, May 31, 2025 at 04:20:02PM -0700, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 80f31d2a7e5f4efa7150c951268236c670bcb068
> Author: Christoph Hellwig <hch@lst.de>
> Date: Thu May 8 05:14:32 2025 +0000
That's not possible; this commit is after the original report.
That said, there _is_ a double folio_unlock() in this patch, which
I'm about to send a fix for. It's just not fixing the original report.
next prev parent reply other threads:[~2025-06-01 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:00 [syzbot] [netfs?] kernel BUG in folio_unlock (3) syzbot
2025-02-20 16:15 ` Matthew Wilcox
2025-02-20 22:05 ` Dominique Martinet
2025-02-21 23:35 ` Hillf Danton
2025-02-21 23:58 ` syzbot
2025-02-26 8:41 ` David Howells
2025-05-31 23:20 ` syzbot
2025-06-01 0:26 ` Matthew Wilcox [this message]
2025-06-11 14:08 ` Aleksandr Nogikh
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=aDueHCMDLPs2UtY2@casper.infradead.org \
--to=willy@infradead.org \
--cc=asmadeus@codewreck.org \
--cc=chao@kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=v9fs@lists.linux.dev \
/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).