On Thu, 25 July 2013 11:16:06 -0400, Dhaval Giani wrote:

quoted

If you want to follow some other approach where userspace has one
interface to write the compressed data to a file and some other
interface to read the file uncompressed, you are likely in a world of
pain.

Why? If it is going to only be a few applications who know the file
is compressed, and read it to get decompressed data, why would it be
painful?

It would likely require an ABI extention.  Your immediate pain would
be to get past a wall of NAK when you propose the extention.  You have
to make a rather convincing case that the ABI extention cannot cause
VFS or filesystem maintainers future pain in some dark cornercase.

Just because the one application you care about only wants to use
compression on write-once files doesn't prevent the next person from
abusing the new ABI.  Such abuse should be strictly limited,
preferrably impossible.

I am not saying that I object.  Just warning you to brace yourself for
impact.

What about introducing a new flag, O_COMPR which tells the
kernel, btw, we want this file to be decompressed if it can be. It
can fallback to O_RDONLY or something like that? That gets rid of
the chattr ugliness.

How is that different from chattr ugliness, which also comes down to a
single flag? ;)

Jörn

--
/* Keep these two variables together */
int bar;