Messages in this thread | | | Date | Mon, 6 Nov 2023 14:44:12 -0500 | Subject | Re: [PATCH] fs: Pass AT_GETATTR_NOSEC flag to getattr interface function | From | Stefan Berger <> |
| |
On 10/10/23 04:35, Christian Brauner wrote: > On Mon, 02 Oct 2023 08:57:33 -0400, Stefan Berger wrote: >> When vfs_getattr_nosec() calls a filesystem's getattr interface function >> then the 'nosec' should propagate into this function so that >> vfs_getattr_nosec() can again be called from the filesystem's gettattr >> rather than vfs_getattr(). The latter would add unnecessary security >> checks that the initial vfs_getattr_nosec() call wanted to avoid. >> Therefore, introduce the getattr flag GETATTR_NOSEC and allow to pass >> with the new getattr_flags parameter to the getattr interface function. >> In overlayfs and ecryptfs use this flag to determine which one of the >> two functions to call. >> >> [...] > > Applied to the vfs.fixes branch of the vfs/vfs.git tree. > Patches in the vfs.fixes branch should appear in linux-next soon.
Did something happen to this patch? I do not see it in your branch nor the linux-next one nor Linus's tree.
> > 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.fixes > > [1/1] fs: Pass AT_GETATTR_NOSEC flag to getattr interface function > https://git.kernel.org/vfs/vfs/c/6ea042691c74
| |