From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Mounting lock_nolock file systems?
Date: Wed, 22 Jun 2022 16:30:07 +0200 [thread overview]
Message-ID: <20220622143007.GA31207@lst.de> (raw)
In-Reply-To: <20220621125857.GA6999@lst.de>
On Tue, Jun 21, 2022 at 02:58:57PM +0200, Christoph Hellwig wrote:
> Sorry, actually it was the pagecache for-next branch from willy. Looks
> like mainline itself is fine.
>
> I'll try to get the superblock information from the pagecache branch
> once I find a little time, chasing a bunch of other bugs in the meantime.
I bisected it down to:
commit 1abe0e8c19c514827408ba7e7e84969b6f2e784f
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Wed May 18 14:41:39 2022 -0400
gfs: Check PageUptodate instead of PageError
This is the correct flag to test to know if the read completed
successfully.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
but I don't have any explanation how it caused that breakage yet.
next prev parent reply other threads:[~2022-06-22 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 9:14 [Cluster-devel] Mounting lock_nolock file systems? Christoph Hellwig
2022-06-21 10:53 ` Andreas Gruenbacher
2022-06-21 11:19 ` Andrew Price
2022-06-21 12:58 ` Christoph Hellwig
2022-06-22 14:30 ` Christoph Hellwig [this message]
2022-06-23 15:44 ` 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=20220622143007.GA31207@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.