On 8/7/06, Pekka Enberg <[email protected]> wrote:
[Albert Cahalan]
Edgar Toernig writes:
> > Urgs, so any user may remove mappings from another process and
> > let it crash?
> 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.
You're right. Apps must already be tolerant of SIGBUS.
There is thus no additional risk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
