On Thu, Jun 05, 2025 at 01:33:57PM -0400, Brian Foster wrote: > iomap_zero_range() has to cover various corner cases that are > difficult to test on production kernels because it is used in fairly > limited use cases. For example, it is currently only used by XFS and > mostly only in partial block zeroing cases. > > While it's possible to test most of these functional cases, we can > provide more robust test coverage by co-opting fallocate zero range > to invoke zeroing of the entire range instead of the more efficient > block punch/allocate sequence. Add an errortag to occasionally > invoke forced zeroing. I like this, having an easy way to improve code coverage using the existing fallocate and errtag interfaces is always a good thing. Can I assume you plan to add a testcase using the errtag to xfstests?
