Re: mlock(1)

[Chris Friesen]

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.

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

Chris
-
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/