From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Albert Cahalan" Subject: Re: [RFC/PATCH] revoke/frevoke system calls Date: Mon, 7 Aug 2006 11:19:47 -0400 Message-ID: <787b0d920608070819u5f93b7c5pb45b323d4c74bde4@mail.gmail.com> References: <787b0d920607220105l21251402nc98381edbc27a0c5@mail.gmail.com> <84144f020608070345q58a9c12btc2eb57cd7bf8dd14@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: froese@gmx.de, B.Steinbrink@gmx.de, hurtta+gmane@siilo.fmi.fi, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from nf-out-0910.google.com ([64.233.182.185]:47621 "EHLO nf-out-0910.google.com") by vger.kernel.org with ESMTP id S932146AbWHGPTv (ORCPT ); Mon, 7 Aug 2006 11:19:51 -0400 Received: by nf-out-0910.google.com with SMTP id p46so492052nfa for ; Mon, 07 Aug 2006 08:19:50 -0700 (PDT) To: "Pekka Enberg" In-Reply-To: <84144f020608070345q58a9c12btc2eb57cd7bf8dd14@mail.gmail.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 8/7/06, Pekka Enberg 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.