On Thu, Jun 05, 2014 at 09:49:29PM -0400, Mimi Zohar wrote: > > > > > There's no mention of this return value in the man page, so I dug > > > > > into the kernel code, and it appears that we do.. > > > > > > > > > > sys_mmap > > > > > vm_mmap_pgoff > > > > > security_mmap_file > > > > > ima_file_mmap <- returns 0 if not PROT_EXEC > > > > > > > > > > and then the 0 gets propagated up as a retval all the way to userspace. > > > > > > I just realised that this affects even kernels with CONFIG_IMA unset, > > > because there we just do 'return 0' unconditionally. > > > > > > Also, it appears that kernels with CONFIG_SECURITY unset will also > > > return a zero for the same reason. > > > > Hang on, I was misreading that whole security_mmap_file ret handling code. > > There's something else at work here. I'll dig and get a reproducer. > > According to security.h, it should return 0 if permission is granted. > If IMA is not enabled, it should also return 0. What exactly is the > problem? Still digging. I managed to get this to reproduce constantly last night, but no luck today. From re-reading the code though, I think IMA/lsm isn't the problem. Dave -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>