mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: linux-kernel@vger.kernel.org
Subject: Automatic namespace switch
Date: Fri, 11 Aug 2006 15:56:25 +0200	[thread overview]
Message-ID: <20060811135625.GA18616@clipper.ens.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

Hi.

I was wondering about one particular feature extending namespaces
functionalities: automatic namespace switching. The principle would be: a
process references several namespaces. One of these namespaces is the actual
namespace the process is living in. During the process lifespan, various
events can cause it to automatically switch to another of its namespaces.

The type of event I am especially interested in is the execve()ing of a
32bit file in the case of the x86_64 architecture: the init process creates
two namespaces, one mounting a 64bit /usr and a 32bit /usr/32 (or maybe
another name), the other mounting the 32bit in /usr and the 64bit in
/usr/64, both sharing /home, /tmp and part of /var. When a program available
only in 32bit is needed, it is exec()ed in /usr/32/bin/ (which is probably
in the PATH), and that fact causes the process to switch to the 32bit
namespace, where the program will find all its libraries and data at the
expected place.

Such a feature would require careful examination about the security
implication. But I believe it may help to make the transition to pure 64bit
systems (which, I fear, will be long) smoother.

Does anyone have remarks about such an idea, be it to explain why it is
stupid?

Regards,

-- 
  Nicolas George

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 185 bytes --]

                 reply	other threads:[~2006-08-11 13:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060811135625.GA18616@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --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

all inboxes | Powered by JetHome®