Re: Non-Exec stack patches
From: John Reiser
Date: Wed Mar 24 2004 - 14:10:55 EST
Only one mprotect() call is needed to make the entire stack
mprotect() only works on the portion that is currently allocated.
If the stack grows, then another call is needed. Tracking the high-
water mark is an expense. Forcing the allocation of the maximum
extent for the stack of the current thread, even to the same copy-
on-write all-zero page, can cause memory overcommit problems.
John Reiser, jreiser@xxxxxxxxxxxx
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/