From: Rik van Riel <riel@nl.linux.org>
To: Christoph Rohland <hans-christoph.rohland@sap.com>
Cc: MM mailing list <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.rutgers.edu>,
"Eric W. Biederman" <ebiederm+eric@ccr.net>,
Alexander Viro <viro@math.psu.edu>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
GOTO Masanori <gotom@debian.or.jp>
Subject: Re: [PATCH] replace SYSV shared memory with shm filesystem
Date: Mon, 10 Jan 2000 13:52:01 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10001101350300.584-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <qwwvh52ruin.fsf_-_@sap.com>
On 10 Jan 2000, Christoph Rohland wrote:
> You can mount the fs only once. This will probably break shm in
> chrooted environments.
I think it would be best to code it in such a way that you
can mount multiple instances of shmfs, in such a way that
the differently chrooted programs cannot see each other's
shared memory. That should make it a bit more difficult to
get out of a chroot() jail...
(security buffs, please tell me if I'm full of it)
cheers,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.nl.linux.org/Linux-MM/
next prev parent reply other threads:[~2000-01-10 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-10 12:17 Christoph Rohland
2000-01-10 12:39 ` Alan Cox
2000-01-10 12:46 ` Christoph Rohland
2000-01-10 12:52 ` Rik van Riel [this message]
2000-01-10 13:59 ` Andi Kleen
2000-01-10 17:55 ` Christoph Rohland
2000-01-10 20:41 ` James Antill
2000-01-11 11:18 ` Richard Guenther
2000-01-11 12:00 ` Christoph Rohland
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=Pine.LNX.4.10.10001101350300.584-100000@mirkwood.dummy.home \
--to=riel@nl.linux.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm+eric@ccr.net \
--cc=gotom@debian.or.jp \
--cc=hans-christoph.rohland@sap.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=viro@math.psu.edu \
/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