Clarifies issues in mprotect with MAP_PRIVATE
authorBarret Rhoden <brho@cs.berkeley.edu>
Tue, 10 Aug 2010 21:22:37 +0000 (14:22 -0700)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 3 Nov 2011 00:35:51 +0000 (17:35 -0700)
commit2f200df65377ef9899c789419159bafb97b4b2b8
tree577492202f8c651d99db2f9c1ec40eed87830e39
parent369acc0a91a048bf74eb1c4cdf4a0f2c0cbfae5d
Clarifies issues in mprotect with MAP_PRIVATE

The main danger here is with dynamically loaded processes overwriting
libc.  Also note that after mprotecting, you may have mergeable VMRs
that aren't merged.
kern/src/mm.c