From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: grendel@caudium.net
Cc: Peter Chubb <peter@chubb.wattle.id.au>,
Jeff Dike <jdike@addtoit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: user- vs kernel-level resource sandbox for Linux?
Date: Tue, 30 Nov 2004 20:20:19 +0000 [thread overview]
Message-ID: <1101846018.25628.155.camel@localhost.localdomain> (raw)
In-Reply-To: <20041130204708.GB14080@beowulf.thanes.org>
On Maw, 2004-11-30 at 20:47, Marek Habersack wrote:
> That's my current impression. I also considered writing a simple kernel
> module to intercept sys_brk, but that seemed to be a bit clumsy. We have
You have to consider kernel side resources too - page tables, memory
maps
and the like which jails don't really fix.
next prev parent reply other threads:[~2004-11-30 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:19 user- vs kernel-level resource sandbox for Linux? Marek Habersack
2004-11-29 20:00 ` Jeff Dike
2004-11-29 22:13 ` Peter Chubb
2004-11-30 2:39 ` Marek Habersack
2004-11-30 18:48 ` Alan Cox
2004-11-30 20:47 ` Marek Habersack
2004-11-30 20:20 ` Alan Cox [this message]
2004-12-02 2:32 ` Herbert Poetzl
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=1101846018.25628.155.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=grendel@caudium.net \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.