On Fri, Dec 19, 2025 at 7:10 PM Christoph Hellwig <[email protected]> wrote: > Well, for the file size you can test by doing a truncate to the expected > size and _notrun if not supported. I can't really think of a way that > easy to directly check for the number of supported blocks.
I guess we can calculate the block limit by _get_max_file_size() / block_size. However, I am concerned whether this method might mask a regression that reduces a filesystem's supported file size. So I wonder if explicit, hardcoded limits within the helper for known architectural constraints (like for F2FS) would be safer, as we can ensure tests are only skipped when the limitation is intended. Please let me know if you have suggestions for either method. Best regards, Joanne _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
