On Mon, 2002-11-18 at 12:26, Ingo Molnar wrote:
>
> and we have VM_DONTCOPY already, which is used by the DRM code. So it
> would only be a question of exporting this API to userspace. The attached
> patch adds MAP_DONTCOPY. I made it unpriviledged, i doubt it has any
> security impact.
What is the behaviour of someone setting VM_DONTCOPY on memory that was
copy on write between a large number of processes (say an executable
image) ? Don't copy - but don't copy from what, from the original
mapping or from the COW mapping of the original mapping ?
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 23 2002 - 22:00:22 EST