On Oct 18, 2018, at 7:11 AM, Miklos Szeredi wrote:
>
> FUSE will want to know if stx_attributes is interesting or not, because
> there's a non-zero cost of retreiving it.
>
> This is more of a "want" flag, since stx_attributes_mask already indicates
> whether we "got" stx_attributes or not. So
On Oct 18, 2018, at 7:11 AM, Miklos Szeredi wrote:
>
> FUSE will want to know if stx_attributes is interesting or not, because
> there's a non-zero cost of retreiving it.
>
> This is more of a "want" flag, since stx_attributes_mask already indicates
> whether we "got" stx_attributes or not. So
Miklos Szeredi wrote:
> + /* Having anything in attributes_mask means attributes are valid. */
> + if (tmp.stx_attributes_mask)
> + tmp.stx_mask |= STATX_ATTRIBUTES;
That would be superfluous, since userspace can make this check too.
Note that fsinfo() might inform you
Miklos Szeredi wrote:
> + /* Having anything in attributes_mask means attributes are valid. */
> + if (tmp.stx_attributes_mask)
> + tmp.stx_mask |= STATX_ATTRIBUTES;
That would be superfluous, since userspace can make this check too.
Note that fsinfo() might inform you
FUSE will want to know if stx_attributes is interesting or not, because
there's a non-zero cost of retreiving it.
This is more of a "want" flag, since stx_attributes_mask already indicates
whether we "got" stx_attributes or not. So for now we can just deal with
this flag in the generic code.
FUSE will want to know if stx_attributes is interesting or not, because
there's a non-zero cost of retreiving it.
This is more of a "want" flag, since stx_attributes_mask already indicates
whether we "got" stx_attributes or not. So for now we can just deal with
this flag in the generic code.
6 matches
Mail list logo
