Messages in this thread | | | Date | Mon, 7 Aug 2006 11:19:47 -0400 | From | "Albert Cahalan" <> | Subject | Re: [RFC/PATCH] revoke/frevoke system calls |
| |
On 8/7/06, Pekka Enberg <penberg@cs.helsinki.fi> 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |