[lkml]   [2018]   [Oct]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 6/5] statx: add STATX_RESULT_MASK flag
On Fri, Oct 19, 2018 at 5:59 PM, David Howells <> wrote:
> Miklos Szeredi <> wrote:
>> FUSE needs this, because it uses legacy inode initialization, that doesn't
>> return a result_mask, so needs a refresh when caller asks for it with
>> statx().
> Can't you just make it up in fuse? Presumably, fuse doesn't support any of
> the non-basic statx fields either?

This is very much about the basic statx fields. I.e. what does
result_mask == STATX_BASIC_STATS means?

a) this is a legacy stat() implementation that doesn't fill in the
result_mask properly

b) this is an up-todate stat() implementation that does fill the
result_mask properly and all fields are valid

There's no way to tell which one it is, and no way to request that
filesystem try b) even if it's more costly.

>> It might make sense later to promote this to a proper statx mask flag and
>> return it in stx_mask to userspace.
> That sounds kind of recursive - a bit in stx_mask would be saying whether or
> not stx_mask can be used.

Yes. See above.

> Please don't use that bit.

Using it internally is perfectly harmless. If we'll need to extend
statx in the future and make use of this flag externally, then we can
easily move the internal flag somewhere else (e.g. extend request_mask
to 64bit, which we'll probably need to do anyway in that case).


 \ /
  Last update: 2018-10-19 19:43    [W:0.058 / U:1.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site