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@xxxxxxxxxx/ 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..
