From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2 is unhappy on pagecache/for-next
Date: Mon, 20 Jun 2022 08:21:47 +0200 [thread overview]
Message-ID: <20220620062147.GB10640@lst.de> (raw)
In-Reply-To: <Yq8TShTaJ6xn6Koi@casper.infradead.org>
On Sun, Jun 19, 2022 at 01:15:06PM +0100, Matthew Wilcox wrote:
> On Sun, Jun 19, 2022 at 09:05:59AM +0200, Christoph Hellwig wrote:
> > When trying to run xfstests on gfs2 (locally with the lock_nolock
> > cluster managed) the first mount already hits this warning in
> > inode_to_wb called from mark_buffer_dirty. This all seems standard
> > code from folio_account_dirtied, so not sure what is going there.
>
> I don't think this is new to pagecache/for-next.
> https://lore.kernel.org/linux-mm/cf8bc8dd-8e16-3590-a714-51203e6f4ba9 at redhat.com/
Indeed, I can reproduce this on mainline as well. I just didn't
expect a maintained file system to blow up on the very first mount
in xfstests..
next prev parent reply other threads:[~2022-06-20 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 7:05 [Cluster-devel] gfs2 is unhappy on pagecache/for-next Christoph Hellwig
2022-06-19 12:15 ` Matthew Wilcox
2022-06-20 6:21 ` Christoph Hellwig [this message]
2022-06-20 17:20 ` 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=20220620062147.GB10640@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 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).