From: ebiederm@xmission.com (Eric W. Biederman)
To: "Albert Cahalan" <acahalan@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@osdl.org>,
akpm@osdl.org, ebiederm@xmission.com, janak@us.ibm.com,
viro@ftp.linux.org.uk, hch@lst.de, ak@muc.de, paulus@samba.org,
mtk-manpages@gmx.net
Subject: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
Date: Mon, 20 Mar 2006 09:52:58 -0700 [thread overview]
Message-ID: <m1oe01vz11.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <787b0d920603192045y76e99e32p4ddde31961f80bb9@mail.gmail.com> (Albert Cahalan's message of "Sun, 19 Mar 2006 23:45:52 -0500")
"Albert Cahalan" <acahalan@gmail.com> writes:
> The unshare() syscall is in fact a clone() syscall minus one
> CLONE_* flag that is normally implied: CLONE_TASK_STRUCT.
> (conceptually -- it has no name because it is always implied)
>
> We already have one flag with inverted action: CLONE_NEWNS.
> Adding another such flag (for the task struct) makes sense.
> The new system call is thus not needed at all.
>
> Suggested names: CLONE_NO_TASK, CLONE_SAMETASK, CLONE_SHARETASK
The practical issue there is that even in the best case the implementations
are enough different that it probably would not make a lot of sense.
Eric
next prev parent reply other threads:[~2006-03-20 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 4:45 Albert Cahalan
2006-03-20 16:52 ` Eric W. Biederman [this message]
[not found] <1359.1142546753@www064.gmx.net>
2006-03-16 23:34 ` Michael Kerrisk
2006-03-16 23:57 ` Linus Torvalds
2006-03-17 1:11 ` Michael Kerrisk
2006-03-17 5:42 ` Linus Torvalds
2006-03-17 16:04 ` Eric W. Biederman
2006-03-17 16:49 ` Janak Desai
2006-03-17 20:27 ` Michael Kerrisk
2006-03-18 18:41 ` Eric W. Biederman
2006-03-18 19:54 ` Janak Desai
2006-03-19 13:58 ` Eric W. Biederman
2006-03-18 23:41 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2006-03-16 16:49 Eric W. Biederman
2006-03-16 19:40 ` Michael Kerrisk
2006-03-16 20:33 ` Andrew Morton
2006-03-16 20:41 ` Linus Torvalds
2006-03-16 21:58 ` Eric W. Biederman
2006-03-16 22:19 ` Andrew Morton
2006-03-16 21:36 ` 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=m1oe01vz11.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=acahalan@gmail.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=janak@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=paulus@samba.org \
--cc=torvalds@osdl.org \
--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
Powered by JetHome