On Mon, Nov 4, 2019 at 11:53 PM Mark Salyzyn <salyzyn@xxxxxxxxxxx> wrote:
Patch series:Sigh.. did not get to fsdevel (again...) I already told you several times
Mark Salyzyn (4):
Add flags option to get xattr method paired to __vfs_getxattr
that you need to use a shorter CC list.
Will do, send it only to fsdevel, other recipients? What do I do with get_maintainer.pl? The first patch in the series is noisy, I am getting more and more uncomfortable sending it to the list as it looks more and more like spam.overlayfs: handle XATTR_NOSECURITY flag for get xattr methodIt would be better for review IMO if you rebase your series on top of
overlayfs: internal getxattr operations without sepolicy checking
overlayfs: override_creds=off option bypass creator_cred
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git ovl-unpriv
1. internal getxattr patch would be a one liner change to ovl_own_getxattr()
2. The documentation of override_creds would be much more
meaningful if it used the overlay permission model terminology
that Miklos added in his patch set and extend it
Thanks,
Amir.