From: Paul Mackerras <paulus@samba.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Linus Torvalds <torvalds@osdl.org>,
Michael Kerrisk <mtk-manpages@gmx.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org, janak@us.ibm.com,
viro@ftp.linux.org.uk, hch@lst.de, ak@muc.de
Subject: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
Date: Sun, 19 Mar 2006 10:41:16 +1100 [thread overview]
Message-ID: <17436.39580.217348.85222@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <m1r74zzjbg.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman writes:
> - We don't confuse users and developers about the inverted values of
> the clone bits.
Given that the name starts with "un", I would *expect*
unshare(CLONE_FOO) to mean that I no longer want to share FOO.
If you want the argument to have the same sense as in the clone system
call, you will have to call it "share" rather than "unshare" (and then
explain to confused developers why they can't use it to start sharing
things that previously weren't shared :).
Paul.
next prev parent reply other threads:[~2006-03-18 23:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2006-03-20 4:45 Albert Cahalan
2006-03-20 16:52 ` Eric W. Biederman
-- 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=17436.39580.217348.85222@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=janak@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--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
all inboxes | Powered by JetHome®