On Wed, Jun 16, 2021 at 05:17:08PM +0000, Frank van der Linden wrote: > > The problem here for xfstests is how to define the 'correct' behavior > across all filesystems so that there's a clean pass/fail, as long > as these inconsistencies exist. Note that the original xfstest in question is to check what happens when you have a pre-existing xattr with a small (16 byte) value, and replacing (overwriting) the xattr with a large (but valid) value. The problem was that generic/486 was using the preferred size for efficient I/O size as the "block" size, and then using a percentage of this "block" size as the arbitrary "large xattr size". It was not about the error codes being returned, which is a bit confusing, and for which different man pages (attr_set and setxattr) are differently incomplete. That's really a different issue, and the fact that different file systems can use different error codes is not necessarily something that we need to rationalize, in particular for file systems like NFS where the error codes returned are not entirely under the control of the NFS client or server code. Cheers, - Ted
