Re: mlock(1)

[Chris Wright]

* Chris Friesen (cfriesen@xxxxxxxxxxxxxxxxxx) wrote:
> Chris Wright wrote:
> 
> > The info is stored in the memory mapping info that's necessarily blown
> > away at execve(2) because that's where you are overlaying a new image.
> 
> Yeah, I just saw that on the man page for mlockall.

It's required for SUSv3 (mlock too).

> I though maybe it was stored on the task struct or something.

Nope, default from MCL_FUTURE is ->mm->def_flags otherwise it's per
vma->vm_flags.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/