Hi,
Edgar Toernig writes:
> Urgs, so any user may remove mappings from another process and
> let it crash?
On 7/22/06, Albert Cahalan <acahalan@xxxxxxxxx> wrote:
Two good solutions come to mind:
a. substitute the zero page
b. make the mapping private and touch it as if C-O-W happened
Actually, I think revokeat() and frevoke() should be consistent with
mmap which will make a process go SIGBUS if it attempts to write to
truncated shared mapping.
Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
