On 8/7/06, Pekka Enberg <penberg@xxxxxxxxxxxxxx> 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-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
