Re: [man-pages RFC PATCH] statx.2: document STATX_ATTR_VERITY
From: walter harms <hidden>
Date: 2019-11-08 08:23:14
Also in:
linux-fscrypt, linux-fsdevel, linux-man
From: walter harms <hidden>
Date: 2019-11-08 08:23:14
Also in:
linux-fscrypt, linux-fsdevel, linux-man
Am 07.11.2019 23:02, schrieb Eric Biggers:
From: Eric Biggers <redacted> Document the verity attribute for statx(). Signed-off-by: Eric Biggers <redacted> --- man2/statx.2 | 4 ++++ 1 file changed, 4 insertions(+) RFC since the kernel patches are currently under review. The kernel patches can be found here: https://lkml.kernel.org/linux-fscrypt/20191029204141.145309-1-ebiggers@kernel.org/T/#udiff --git a/man2/statx.2 b/man2/statx.2 index d2f1b07b8..713bd1260 100644 --- a/man2/statx.2 +++ b/man2/statx.2@@ -461,6 +461,10 @@ See .TP .B STATX_ATTR_ENCRYPTED A key is required for the file to be encrypted by the filesystem. +.TP +.B STATX_ATTR_VERITY +The file has fs-verity enabled. It cannot be written to, and all reads from it +will be verified against a Merkle tree.
Using "Merkle tree" opens a can of worm and what will happen when the methode will change ? Does it matter at all ? i would suggest "filesystem" here. re, wh
.SH RETURN VALUE On success, zero is returned. On error, \-1 is returned, and