linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Albert Cahalan" <acahalan@gmail.com>
Cc: froese@gmx.de, B.Steinbrink@gmx.de, hurtta+gmane@siilo.fmi.fi,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC/PATCH] revoke/frevoke system calls
Date: Mon, 7 Aug 2006 13:45:20 +0300	[thread overview]
Message-ID: <84144f020608070345q58a9c12btc2eb57cd7bf8dd14@mail.gmail.com> (raw)
In-Reply-To: <787b0d920607220105l21251402nc98381edbc27a0c5@mail.gmail.com>

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@gmail.com> 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

  reply	other threads:[~2006-08-07 10:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-22  8:05 [RFC/PATCH] revoke/frevoke system calls Albert Cahalan
2006-08-07 10:45 ` Pekka Enberg [this message]
2006-08-07 15:19   ` Albert Cahalan
     [not found] <6AFvY-7ZK-15@gated-at.bofh.it>
2006-07-20 21:26 ` Bodo Eggert
2006-07-20 23:01   ` roucaries bastien
  -- strict thread matches above, loose matches on Subject: below --
2006-07-20 12:07 Pekka J Enberg
2006-07-20 20:02 ` Kari Hurtta
2006-07-20 21:09   ` Björn Steinbrink
2006-07-21 22:16     ` Edgar Toernig
2006-07-22  0:19 ` Andrew Morton
2006-07-22  6:22   ` Pekka J Enberg
2006-07-22  6:59     ` Andrew Morton
2006-07-22  7:41       ` Pekka Enberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84144f020608070345q58a9c12btc2eb57cd7bf8dd14@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=B.Steinbrink@gmx.de \
    --cc=acahalan@gmail.com \
    --cc=froese@gmx.de \
    --cc=hurtta+gmane@siilo.fmi.fi \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).