On Oct 17, 2018, at 1:04 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > > On Wed, Oct 17, 2018 at 8:45 PM, Andreas Dilger <adilger@xxxxxxxxx> wrote: >> On Oct 17, 2018, at 12:24 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: >>> >>> I'm trying to implement statx for fuse and ran into the following issues: >>> >>> - Need a STATX_ATTRIBUTES bit, so that userspace can explicitly ask >>> for stx_attribute; otherwise if querying has non-zero cost, then >>> filesystem cannot do it without regressing performance. >> >> Seems reasonable. >> >>> - STATX_ALL definition is unclear, can this change, or is it fixed? >>> If it's the former, than that's a backward compatibility nightmare. >>> If it's the latter, then what's the point? >> >> The value can change over time. It is intended to reflect the current >> state of affairs at the time the userspace program and kernel are compiled. >> The value sent from userspace lets the kernel know what fields are in >> the userspace struct, so it doesn't try to set fields that aren't there. > > What's the point of a userspace program specifying STATX_ALL? Without > a way to programmatically query the interface definition it's useless: > there's no way to guess which mask bit corresponds to which field, and > what that field represents. > > And there will be programs out there which specify STATX_ALL without > considering that in the future it may become slower as it is now due > to a recompile. The whole point of statx is that applications should only be requesting fields that they care about, so "ls --color=never" shouldn't be asking for the file mode/size/etc., and size/blocks should only be requested with "ls -ls", etc. > So what's the point exactly? Ah, I see your point... STATX_ALL seems to be mostly useful for the kernel to mask off flags that it doesn't currently understand. It doesn't make much sense for applications to specify STATX_ALL, since they don't have any way to know what each flag means unless they are hard-coded to check each of the STATX_* flags individually. They should build up a mask of STATX_* flags based on what they care about (e.g. "find" should only request attributes based on the command-line options given). >> The value in the kernel allows masking off new fields from userspace that >> it doesn't understand. > > Okay, but that has nothing to do with the UAPI. Even as an internal > flag we should be careful, as it might grow uses which can have > similar issues as the userspace one above. > >>> - STATX_ATIME is cleared from stx_mask on SB_RDONLY, and on NFS it is >>> also cleared on MNT_NOATIME, but not on MNT_RDONLY. We need some sort >>> of guideline in the documentation about what constitutes >>> "unsupported": does atime become unsupported because filesystem is >>> remounted r/o? If so, why isn't this case handled consistently in the >>> VFS and filesystems? >> >> Strange. I'd think that if userspace is requesting atime, it should >> get an atime value. The fact that the kernel is not updating atime >> due to mount options just means that atime might be old. That doesn't >> mean (IMHO) that atime doesn't exist. > > Right, OTOH I sort of see the value in NFS: no roundtrip to server if > atime value is useless anyway. Well, "noatime" might be a client-only option, which doesn't mean that the server or some other client isn't updating the atime. Returning an old atime isn't the same as not returning anything at all. >>> - What about fields that are not cached when statx() is called with >>> AT_STATX_DONT_SYNC? E.g. stx_btime is supported by the filesystem, >>> but getting it requires a roundtrip to the server. Requesting >>> STATX_BTIME in the mask and adding AT_STATX_DONT_SYNC to the flags >>> means the filesystem has to decide which it will honor. My feeling >>> is that it should honor AT_STATX_DONT_SYNC and clear STATX_BTIME in >>> stx_mask. Documentation has no word about this case. >> >> The btime value shouldn't change over the lifetime of a file, so >> DONT_SYNC shouldn't have any effect on its validity? > > Not validity, but presence in the cache. Network filesystem or fuse > may or may not have it available in the cache at the time the inode is > first initialized on loookup. So when statx(..., AT_STATX_DONT_SYNC, > STATX_BTIME) comes along, it may need a roundtrip to the server. What > should it do? To my thinking, if the user/app requests btime/ctime/size/blocks the kernel should return these fields. If DONT_SYNC is set, it means the kernel can return potentially stale values, but if the kernel doesn't have *any* values for these fields at all it still should query the server instead of just returning random garbage. That said, it seems that it isn't even possible to get into nfs_getattr() without the VFS having instantiated a dentry and inode (i.e. queried the server via nfs_lookup() at some point), so the inode fields have already been filled with *something*. Cheers, Andreas
Attachment:
signature.asc
Description: Message signed with OpenPGP
