From: JANAK DESAI <janak@us.ibm.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Ingo Molnar <mingo@elte.hu>,
chrisw@osdl.org, dwmw2@infradead.org, jamie@shareable.org,
serue@us.ibm.com, linuxram@us.ibm.com, jmorris@namei.org,
sds@tycho.nsa.gov, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/5] New system call, unshare
Date: Fri, 09 Dec 2005 09:48:39 -0500 [thread overview]
Message-ID: <43999947.5020300@us.ibm.com> (raw)
In-Reply-To: <20051209143445.GM27946@ftp.linux.org.uk>
Al Viro wrote:
>On Fri, Dec 09, 2005 at 09:15:53AM -0500, JANAK DESAI wrote:
>
>
>>To answer Ingo's question, we did look at other flags when I started.
>>However,
>>I wanted to keep the system call simple enough, with atleast namespace
>>unsharing,
>>so it would get accepted. In the original discussion on fsdevel,
>>unsharing of vm
>>was mentioned as useful so I added that in addition to namespace unsharing.
>>
>>
>
>So make that a series... Note that it can be merged gradually - adding
>and debugging the unsharing of fs, files, etc. can be done independently
>and with no ABI changes.
>
>
Ok, thanks. Will do.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
next prev parent reply other threads:[~2005-12-09 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 22:09 [PATCH -mm 1/5] New system call, unshare JANAK DESAI
2005-12-09 10:55 ` Ingo Molnar
2005-12-09 12:02 ` Al Viro
2005-12-09 14:15 ` JANAK DESAI
2005-12-09 14:34 ` Al Viro
2005-12-09 14:48 ` JANAK DESAI [this message]
2005-12-09 19:01 ` Ingo Molnar
2005-12-09 19:57 ` 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=43999947.5020300@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.