On Fri, 26 Apr 2024 18:20:15 +0200, Christian Göttsche wrote: > Rename the struct xattr_ctx to increase distinction with the about to be > added user API struct xattr_args. > > No functional change. > > So I've picked that series up as this is still a useful addition. Obviously too late for this merge window. However, I stated multiple times that we're not going to add *xattrat() variants that allow to set or get xattrs with AT_EMPTY_PATH on O_PATH file descriptors. Not just because conceptually setting and getting xattrs should be treated akin to read/write wrt to O_PATH but also because it makes the concept of an O_PATH more and more meaningless if we can do ever more things we it. But it will also break assumptions of code that would be surprised if an O_PATH fd suddenly can be used to set and get xattr. So I'll fix it up so AT_EMPTY_PATH is handled to exclude O_PATH file descriptors. --- Applied to the vfs.xattr branch of the vfs/vfs.git tree. Patches in the vfs.xattr branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.xattr [1/2] fs: rename struct xattr_ctx to kernel_xattr_ctx https://git.kernel.org/vfs/vfs/c/836c8e8bb147 [2/2] fs/xattr: add *at family syscalls https://git.kernel.org/vfs/vfs/c/71491cbe0205
