[lkml]   [2004]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: mlock(1)
* Chris Friesen ( wrote:
> Chris Wright wrote:
> > 2. Problem is the execve(2) that the mlock(1) program would have to call.
> > This blows away the mappings which contain the locking info.
> Does it? The man page said it isn't inherited on fork(), but why wouldn't it
> be inherited on exec()?

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.

Linux Security Modules
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:06    [W:0.138 / U:2.700 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site