diff options
| author | Amir Goldstein <[email protected]> | 2024-10-11 09:00:22 +0000 |
|---|---|---|
| committer | Christian Brauner <[email protected]> | 2024-11-15 10:34:57 +0000 |
| commit | c374196b2b9f4b803fccd59ed82f0712041e21e1 (patch) | |
| tree | f8ac07aa4e5f901cf554c6207447d514777d1fc0 /rust/helpers/task.c | |
| parent | fs: prepare for "explicit connectable" file handles (diff) | |
| download | kernel-c374196b2b9f4b803fccd59ed82f0712041e21e1.tar.gz kernel-c374196b2b9f4b803fccd59ed82f0712041e21e1.zip | |
fs: name_to_handle_at() support for "explicit connectable" file handles
nfsd encodes "connectable" file handles for the subtree_check feature,
which can be resolved to an open file with a connected path.
So far, userspace nfs server could not make use of this functionality.
Introduce a new flag AT_HANDLE_CONNECTABLE to name_to_handle_at(2).
When used, the encoded file handle is "explicitly connectable".
The "explicitly connectable" file handle sets bits in the high 16bit of
the handle_type field, so open_by_handle_at(2) will know that it needs
to open a file with a connected path.
old kernels will now recognize the handle_type with high bits set,
so "explicitly connectable" file handles cannot be decoded by
open_by_handle_at(2) on old kernels.
The flag AT_HANDLE_CONNECTABLE is not allowed together with either
AT_HANDLE_FID or AT_EMPTY_PATH.
Signed-off-by: Amir Goldstein <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Fixes: 570df4e9c23f ("ceph: snapshot nfs re-export")
Acked-by:
Reviewed-by: Jeff Layton <[email protected]>
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions
