From: JANAK DESAI <janak@us.ibm.com>
To: viro@ftp.linux.org.uk, chrisw@osdl.org, dwmw2@infradead.org,
jamie@shareable.org, serue@us.ibm.com, mingo@elte.hu,
linuxram@us.ibm.com, jmorris@namei.org, sds@tycho.nsa.gov,
janak@us.ibm.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH -mm 0/9] unshare system call : updated patch series
Date: Tue, 13 Dec 2005 17:54:31 -0500 [thread overview]
Message-ID: <1134513864.11972.156.camel@hobbs.atlanta.ibm.com> (raw)
The following patches represent the updated version of the proposed
new system call unshare. Patches that registered system call for
different architectures were not updated but are being resent in
the series along with the updated patches.
Changes since the first submission of this patch series on 12/12/05:
- Patches 1, 6, 7, 8, and 9 are updated to incorporate
feedback from Al Viro. Changes are described in the change
log for each of the patches (12/13/05)
unshare allows a process to disassociate part of the process context (vm
namespace, files and fs) that was being shared with a parent. Unshare
is needed to implement polyinstantiated directories (such as per-user
and/or per-security context /tmp directory) using the kernel's per-process
namespace mechanism. For a more detailed description of the justification
and approach, please refer to lkml threads from 8/8/05, 10/13/05 & 12/08/05.
Unshare system call, along with shared tree patches, have been in use
in our department for over month and half. We have been using them to
maintain per-user and per-context /tmp directory. The latest port to
2.6.15-rc5-mm2 has been tested on a uni-processor i386 machine.
Patches are organized as follows:
1. Patch implements system call handler sys_unshare. System call
accepts all clone(2) flags but returns -EINVAL when attempt is
made to unshare any shared context.
2. Patch registers system call for i386 architecture
3. Patch registers system call for powerpc architecture
4. Patch registers system call for ppc architecture
5. Patch registers system call for x86_64 architecture
6. Patch implements unsharing of filesystem information
7. Patch implements unsharing of namespace
8. Patch implements unsharing of vm
9. Patch implements unsharing of files
next reply other threads:[~2005-12-13 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 22:54 JANAK DESAI [this message]
2005-12-14 0:19 ` Andrew Morton
2005-12-14 13:02 ` JANAK DESAI
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=1134513864.11972.156.camel@hobbs.atlanta.ibm.com \
--to=janak@us.ibm.com \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=jamie@shareable.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mingo@elte.hu \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.com \
--cc=viro@ftp.linux.org.uk \
/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®