Re: [PATCH 05/11] Creation of "check_vmflags" LSM hook

2017-06-13 Thread Salvatore Mesoraca
2017-06-12 23:31 GMT+02:00 Casey Schaufler : > Have the hook return a value and return that rather > than -EPERM. That way a security module can choose an > error that it determines is appropriate. It is possible > that a module might want to deny the access for a reason > other than lack of privil

Re: [PATCH 05/11] Creation of "check_vmflags" LSM hook

2017-06-13 Thread Salvatore Mesoraca
2017-06-13 8:34 GMT+02:00 Christoph Hellwig : > Please always post the whole series including the users, thanks. I'm sorry for the inconvenience, it won't happen again. Thank you for your comment.

Re: [PATCH 05/11] Creation of "check_vmflags" LSM hook

2017-06-12 Thread Christoph Hellwig
On Mon, Jun 12, 2017 at 06:56:54PM +0200, Salvatore Mesoraca wrote: > Creation of a new LSM hook to check if a given configuration of vmflags, > for a new memory allocation request, should be allowed or not. > It's placed in "do_mmap", "do_brk_flags" and "__install_special_mapping". Please always

Re: [PATCH 05/11] Creation of "check_vmflags" LSM hook

2017-06-12 Thread Casey Schaufler
On 6/12/2017 9:56 AM, Salvatore Mesoraca wrote: > Creation of a new LSM hook to check if a given configuration of vmflags, > for a new memory allocation request, should be allowed or not. > It's placed in "do_mmap", "do_brk_flags" and "__install_special_mapping". > > Signed-off-by: Salvatore Mesora