On Tue, 30 Mar 2021, Joerg Sonnenberger wrote:
This is a bug in the FUSE layer. It should really sanitize the input and not force it on any consumer.
Returning 0 for some of the fields, esp. f_iosize--which is what's the cause of bug #56083--is not wrong, I think. According to statvfs(5): struct statvfs { ... unsigned long f_iosize; ... }; Returning a -1 for that field is probably not right, even if that's what libarchive seems to expect. And, POSIX doesn't say anythng about these implementation-specific fields. -RVP