On Tue, Jul 16, 2024 at 06:46:40PM +0100, Matthew Wilcox wrote:
> On Tue, Jul 16, 2024 at 10:40:16AM -0700, Darrick J. Wong wrote:
> > On Tue, Jul 16, 2024 at 04:29:05PM +0100, Matthew Wilcox wrote:
> > > On Mon, Jul 15, 2024 at 11:44:57AM +0200, Pankaj Raghav (Samsung) wrote:
> > > > +++ b/fs/xfs/xfs_super.c
> > > > @@ -1638,16 +1638,30 @@ xfs_fs_fill_super(
> > > > goto out_free_sb;
> > > > }
> > > >
> > > > - /*
> > > > - * Until this is fixed only page-sized or smaller data blocks work.
> > > > - */
> > > > if (mp->m_sb.sb_blocksize > PAGE_SIZE) {
> > > > - xfs_warn(mp,
> > > > - "File system with blocksize %d bytes. "
> > > > - "Only pagesize (%ld) or less will currently work.",
> > > > + size_t max_folio_size = mapping_max_folio_size_supported();
> > > > +
> > > > + if (!xfs_has_crc(mp)) {
> > > > + xfs_warn(mp,
> > > > +"V4 Filesystem with blocksize %d bytes. Only pagesize (%ld) or less is supported.",
> > > > mp->m_sb.sb_blocksize, PAGE_SIZE);
> > > > - error = -ENOSYS;
> > > > - goto out_free_sb;
> > > > + error = -ENOSYS;
> > > > + goto out_free_sb;
> > > > + }
> > > > +
> > > > + if (mp->m_sb.sb_blocksize > max_folio_size) {
> > > > + xfs_warn(mp,
> > > > +"block size (%u bytes) not supported; maximum folio size supported in "\
> > > > +"the page cache is (%ld bytes). Check MAX_PAGECACHE_ORDER (%d)",
> > > > + mp->m_sb.sb_blocksize, max_folio_size,
> > > > + MAX_PAGECACHE_ORDER);
> > >
> > > Again, too much message. Way too much. We shouldn't even allow block
> > > devices to be created if their block size is larger than the max supported
> > > by the page cache.
> >
> > Filesystem blocksize != block device blocksize. xfs still needs this
> > check because one can xfs_copy a 64k-fsblock xfs to a hdd with 512b
> > sectors and try to mount that on x86.
> >
> > Assuming there /is/ some fs that allows 1G blocksize, you'd then really
> > want a mount check that would prevent you from mounting that.
>
> Absolutely, we need to have an fs blocksize check in the fs (if only
> because fs fuzzers will put random values in fields and expect the system
> to not crash). But that should have nothing to do with page cache size.
Ok, now I am not sure if I completely misunderstood the previous
comments.
One of the comments you gave in the previous series is this[1]:
```
> What are callers supposed to do with an error? In the case of
> setting up a newly allocated inode in XFS, the error would be
> returned in the middle of a transaction and so this failure would
> result in a filesystem shutdown.
I suggest you handle it better than this. If the device is asking for a
blocksize > PMD_SIZE, you should fail to mount it. If the device is
asking for a blocksize > PAGE_SIZE and CONFIG_TRANSPARENT_HUGEPAGE is
not set, you should also decline to mount the filesystem.
```
That is exactly what we are doing here. We check for what can page cache
support and decline to mount if the max order supported is less than the
block size of the filesystem.
Maybe we can trim the the error message to just:
"block size (%u bytes) not supported; Only block size (%ld) or less is supported "\
mp->m_sb.sb_blocksize,
max_folio_size);
Let me know what you think.
[1]https://lore.kernel.org/linux-fsdevel/Zoc2rCPC5thSIuoR@xxxxxxxxxxxxxxxxxxxx/
