From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Janak Desai <janak@us.ibm.com>,
sds@tycho.nsa.gov, linuxram@us.ibm.com, ericvh@gmail.com,
dwalsh@redhat.com, jmorris@redhat.com, akpm@osdl.org,
torvalds@osdl.org, gh@us.ibm.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] New system call, unshare
Date: Tue, 23 Aug 2005 07:07:40 +0100 [thread overview]
Message-ID: <20050823060740.GD9322@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1123512366.31229.8.camel@localhost.localdomain>
On Mon, Aug 08, 2005 at 03:46:06PM +0100, Alan Cox wrote:
> On Llu, 2005-08-08 at 09:33 -0400, Janak Desai wrote:
> >
> > [PATCH 1/2] unshare system call: System Call handler function sys_unshare
>
>
> Given the complexity of the kernel code involved and the obscurity of
> the functionality why not just do another clone() in userspace to
> unshare the things you want to unshare and then _exit the parent ?
Because you want to keep children? Because you don't want to deal with
the implications for sessions/groups/etc.?
FWIW, syscall makes sense. It is a valid primitive and the only reason
to keep it out of clone() (i.e. not making it just another flag to clone())
is that clone() is already cluttered _and_ uses bad calling conventions
for that stuff ("I want to retain <list>" rather than "I want private <list>").
prev parent reply other threads:[~2005-08-23 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 13:33 [PATCH 1/2] New system call, unshare Janak Desai
2005-08-08 14:46 ` Alan Cox
2005-08-08 14:41 ` serge
2005-08-08 15:37 ` Avi Kivity
2005-08-23 6:07 ` Al Viro [this message]
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=20050823060740.GD9322@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwalsh@redhat.com \
--cc=ericvh@gmail.com \
--cc=gh@us.ibm.com \
--cc=janak@us.ibm.com \
--cc=jmorris@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=sds@tycho.nsa.gov \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).