[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230810155225.GD28000@lst.de>
Date: Thu, 10 Aug 2023 17:52:25 +0200
From: Christoph Hellwig <hch@....de>
To: Matthew Wilcox <willy@...radead.org>
Cc: Christoph Hellwig <hch@....de>, Al Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Namjae Jeon <linkinjeon@...nel.org>,
Sungjong Seo <sj1557.seo@...sung.com>,
Theodore Ts'o <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Konstantin Komarov <almaz.alexandrovich@...agon-software.com>,
"Darrick J. Wong" <djwong@...nel.org>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
ntfs3@...ts.linux.dev, linux-xfs@...r.kernel.org
Subject: Re: [PATCH 07/13] xfs: document the invalidate_bdev call in
invalidate_bdev
On Thu, Aug 10, 2023 at 04:22:15PM +0100, Matthew Wilcox wrote:
> > blkdev_issue_flush(mp->m_logdev_targp->bt_bdev);
> > invalidate_bdev(mp->m_logdev_targp->bt_bdev);
>
> While I have no complaints with this as a commit message, it's just too
> verbose for an inline comment, IMO. Something pithier and more generic
> would seem appropriate. How about:
>
> /*
> * Prevent userspace (eg blkid or xfs_db) from seeing stale data.
> * XFS is not coherent with the bdev's page cache.
> */
Well, this completely misses the point. The point is that XFS should
never have to invalidate the page cache because it's not using it,
but it has to due to weird races. I tried to condese the message but
I could not come up with a good one that's not losing information.
Powered by blists - more mailing lists