diff options
author | Christian Brauner <brauner@kernel.org> | 2024-11-15 11:50:59 +0100 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2024-11-15 11:50:59 +0100 |
commit | 2cc789654a36e2561c2c96332a684e351b10f13f (patch) | |
tree | b4d1b23a7e90a1224d16854080e829d6e27f9010 /rust/helpers/build_bug.c | |
parent | b4201b51d93eac77f772298a96bfedbdb0c7150c (diff) | |
parent | 92f3da0d9276f921af49a05c2684fca45e1f1c21 (diff) | |
download | linux-2cc789654a36e2561c2c96332a684e351b10f13f.tar.gz linux-2cc789654a36e2561c2c96332a684e351b10f13f.tar.bz2 linux-2cc789654a36e2561c2c96332a684e351b10f13f.zip |
Merge patch series "ecryptfs: convert to the new mount API"
Eric Sandeen <sandeen@redhat.com> says:
This is lightly tested with the kernel tests present in ecryptfs-utils,
but it could certainly use a bit more testing and review, particularly
with invalid mount option sets.
This one is a little unique compared to other filesystems in that I
allocate both an fs context and the *sbi in .init_fs_context; the *sbi
is long-lived, and the context is only present during the initial mount.
Allocating sbi with the filesystem context means we can set options
into it directly, rather than needing to do it after parsing. And it's
particularly simple to do it this way given that there is no remount.
* patches from https://lore.kernel.org/r/20241028143359.605061-1-sandeen@redhat.com:
ecryptfs: Convert ecryptfs to use the new mount API
ecryptfs: Factor out mount option validation
Link: https://lore.kernel.org/r/20241028143359.605061-1-sandeen@redhat.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'rust/helpers/build_bug.c')
0 files changed, 0 insertions, 0 deletions