On Tue, Nov 12, 2013 at 8:07 PM, Hugo Mills wrote:
> On Tue, Nov 12, 2013 at 08:04:47PM +, Filipe David Manana wrote:
>> On Tue, Nov 12, 2013 at 7:24 PM, Goffredo Baroncelli
>> wrote:
>> > Hi Filipe,
>>
>> Hi
>>
>> >
>> > On 2013-11-12 14:42, Filipe David Borba Manana wrote:
>> >> This chang
On Tue, Nov 12, 2013 at 08:04:47PM +, Filipe David Manana wrote:
> On Tue, Nov 12, 2013 at 7:24 PM, Goffredo Baroncelli
> 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
> >
On Tue, Nov 12, 2013 at 7:24 PM, Goffredo Baroncelli 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 t
Hi Filipe,
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
This change adds infrastructure to allow for generic properties for
inodes via a new ioctl. Properties are name/value pairs that can be
associated with inodes for different purposes. They're stored as
xattrs with the prefix "btrfs."
Properties can be inherited - this means when a directory inode h
