> On Tue, May 07, 2024 at 10:18:46AM +0200, Petr Vorel wrote: > > > Hi! > > > > > > Quite likely, other filesystems does have an inode flag that is set > > > > > > when > > > > > > file has been compressed and simply report that in the foo_getattr() > > > > > > callback. Looking at bcachefs I supose that we need to figure out > > > > > > if the > > > > > > inode is v3 and then unpack the v3 info to get to the compressed > > > > > > flag, > > > > > > you probably know best how to do that.
> > > > > I'm still not clear how we want to map STATX_ATTR_COMPRESSED, since > > > > > it's > > > > > extents that are compressed, not entire files - and just reporting the > > > > > compression option is probably not what we want since it can be > > > > > flipped > > > > > off, and existing data will still be compressed. > > > > > Do you know anything about the intended use case? > > > > As far as I understand the flag it's a hint that the file I/O may be > > > > slower/need more memory because of the compression. > > > Ping. > > > Kent we are getting closer to a next LTP release, are you going to add > > > the compressed flag support into bcachefs or should we add bcachefs to > > > the test skiplist? > > Kent, gentle ping ^. > Add it to the skiplist for now, thanks Thanks, whitelist merged with your ABT. Kind regards, Petr
