Re: [PATCH v17 1/4] Add flags option to get xattr method paired to __vfs_getxattr

2020-10-22 Thread Paul Moore
On Wed, Oct 21, 2020 at 8:07 AM Mark Salyzyn wrote: > On 10/20/20 6:17 PM, Paul Moore wrote: > > On Tue, Oct 20, 2020 at 3:17 PM Mark Salyzyn wrote: > >> Add a flag option to get xattr method that could have a bit flag of > >> XATTR_NOSECURITY passed to it. XATTR_NOSECURITY is generally then > >

Re: [PATCH v17 1/4] Add flags option to get xattr method paired to __vfs_getxattr

2020-10-21 Thread Mark Salyzyn
On 10/20/20 6:17 PM, Paul Moore wrote: On Tue, Oct 20, 2020 at 3:17 PM Mark Salyzyn wrote: Add a flag option to get xattr method that could have a bit flag of XATTR_NOSECURITY passed to it. XATTR_NOSECURITY is generally then set in the __vfs_getxattr path when called by security infrastructure

Re: [PATCH v17 1/4] Add flags option to get xattr method paired to __vfs_getxattr

2020-10-20 Thread Paul Moore
On Tue, Oct 20, 2020 at 3:17 PM Mark Salyzyn wrote: > > Add a flag option to get xattr method that could have a bit flag of > XATTR_NOSECURITY passed to it. XATTR_NOSECURITY is generally then > set in the __vfs_getxattr path when called by security > infrastructure. > > This handles the case of a

[PATCH v17 1/4] Add flags option to get xattr method paired to __vfs_getxattr

2020-10-20 Thread Mark Salyzyn
Add a flag option to get xattr method that could have a bit flag of XATTR_NOSECURITY passed to it. XATTR_NOSECURITY is generally then set in the __vfs_getxattr path when called by security infrastructure. This handles the case of a union filesystem driver that is being requested by the security l