linux-kernel - Re: [RFC/PATCH] revoke/frevoke system calls

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <787b0d920608070819u5f93b7c5pb45b323d4c74bde4@mail.gmail.com>
Date:	Mon, 7 Aug 2006 11:19:47 -0400
From:	"Albert Cahalan" <acahalan@...il.com>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	froese@....de, B.Steinbrink@....de, hurtta+gmane@...lo.fmi.fi,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [RFC/PATCH] revoke/frevoke system calls

On 8/7/06, Pekka Enberg <penberg@...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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/