diff options
author | Christian Brauner <brauner@kernel.org> | 2022-09-22 17:17:18 +0200 |
---|---|---|
committer | Christian Brauner (Microsoft) <brauner@kernel.org> | 2022-10-20 10:13:30 +0200 |
commit | 86c261b9eb4ce0a4ae189c0317cd8eddb8302d5a (patch) | |
tree | f61c06519e08138d3eaf4338bdbda7b6fc4e115e /fs/overlayfs/overlayfs.h | |
parent | af84016f1cfe78b23c8efbf6ba5c3c660d52a9ee (diff) | |
download | linux-86c261b9eb4ce0a4ae189c0317cd8eddb8302d5a.tar.gz linux-86c261b9eb4ce0a4ae189c0317cd8eddb8302d5a.tar.bz2 linux-86c261b9eb4ce0a4ae189c0317cd8eddb8302d5a.zip |
ecryptfs: implement set acl method
The current way of setting and getting posix acls through the generic
xattr interface is error prone and type unsafe. The vfs needs to
interpret and fixup posix acls before storing or reporting it to
userspace. Various hacks exist to make this work. The code is hard to
understand and difficult to maintain in it's current form. Instead of
making this work by hacking posix acls through xattr handlers we are
building a dedicated posix acl api around the get and set inode
operations. This removes a lot of hackiness and makes the codepaths
easier to maintain. A lot of background can be found in [1].
In order to build a type safe posix api around get and set acl we need
all filesystem to implement get and set acl.
So far ecryptfs didn't implement get and set acl inode operations
because it wanted easy access to the dentry. Now that we extended the
set acl inode operation to take a dentry argument and added a new get
acl inode operation that takes a dentry argument we can let ecryptfs
implement get and set acl inode operations.
Note, until the vfs has been switched to the new posix acl api this
patch is a non-functional change.
Link: https://lore.kernel.org/all/20220801145520.1532837-1-brauner@kernel.org [1]
Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>
Diffstat (limited to 'fs/overlayfs/overlayfs.h')
0 files changed, 0 insertions, 0 deletions