diff options
author | Richard Yao <[email protected]> | 2019-03-16 20:43:13 -0400 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2021-08-17 10:25:58 -0700 |
commit | abbf0bd4eba8c44e370c343b1a3ab74f13fd0840 (patch) | |
tree | c124cca6e71790e9d22f99d3adc5dd07bd3612a3 /tests/runfiles/common.run | |
parent | 0f402668f99474b7bd7e1db684186d770ce7f9b6 (diff) |
Linux 4.11 compat: statx support
Linux 4.11 added a new statx system call that allows us to expose crtime
as btime. We do this by caching crtime in the znode to match how atime,
ctime and mtime are cached in the inode.
statx also introduced a new way of reporting whether the immutable,
append and nodump bits have been set. It adds support for reporting
compression and encryption, but the semantics on other filesystems is
not just to report compression/encryption, but to allow it to be turned
on/off at the file level. We do not support that.
We could implement semantics where we refuse to allow user modification
of the bit, but we would need to do a dnode_hold() in zfs_znode_alloc()
to find out encryption/compression information. That would introduce
locking that will have a minor (although unmeasured) performance cost.
It also would be inferior to zdb, which reports far more detailed
information. We therefore omit reporting of encryption/compression
through statx in favor of recommending that users interested in such
information use zdb.
Reviewed-by: Tony Nguyen <[email protected]>
Reviewed-by: Allan Jude <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Reviewed-by: Alexander Motin <[email protected]>
Reviewed-by: Ryan Moeller <[email protected]>
Signed-off-by: Richard Yao <[email protected]>
Closes #8507
Diffstat (limited to 'tests/runfiles/common.run')
0 files changed, 0 insertions, 0 deletions