On Tue, Nov 12, 2013 at 7:24 PM, Goffredo Baroncelli <kreijack@xxxxxxxxx> wrote:
> Hi Filipe,
Hi
>
> On 2013-11-12 14:42, Filipe David Borba Manana wrote:
>> This change adds infrastructure to allow for generic properties for
>> inodes via a new ioctl.
>
> I am sure that there is a valid reason, but I was not able to find it:
> why implement a new ioctl instead of using the *{set,get)xattr(2) syscall ?
Those require one of the following name prefixes: "user.",
"security.", "trusted." or "system.". Only "user." can be set from
user space and requires no special privileges/capabilities (if you
have the necessary permissions on the target inode).
It could be implemented via the "user." prefix, like
"user.btrfs.something" for example - but it can break user
applications if they use such prefix already, and we want to validate
the values set for such properties too.
>
> I noticed that you implemented the Compression properties set/get: is
> this from "chattr -c" ?
With chattr -c you can't specify the compression algorithm - it will
use the default (zlib) or the one you specified via mount options.
thanks
>
> [... cut other lines ... ]
>
> G.Baroncelli
>
> --
> gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
