From: Ingo Molnar <mingo@elte.hu>
To: JANAK DESAI <janak@us.ibm.com>
Cc: viro@ftp.linux.org.uk, 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 0/9] unshare system call (take 3)
Date: Tue, 13 Dec 2005 12:20:29 +0100 [thread overview]
Message-ID: <20051213112029.GA14653@elte.hu> (raw)
In-Reply-To: <1134441527.14136.1.camel@hobbs.atlanta.ibm.com>
* JANAK DESAI <janak@us.ibm.com> wrote:
> Patches are organized as follows:
>
> 1. Patch implementing 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 registering system call for i386 architecture
> 3. Patch registering system call for powerpc architecture
> 4. Patch registering system call for ppc architecture
> 5. Patch registering system call for x86_64 architecture
> 6. Patch implementing unsharing of filesystem information
> 7. Patch implementing unsharing of namespace
> 8. Patch implementing unsharing of vm
> 9. Patch implementing unsharing of files
>
> Unsharing of singnal handlers is still not implemented. As far as I
> can tell, issues raised by Chris Wright regarding possible problems
> stemming from interaction of timers with unsharing of signal handlers,
> has been resolved by a 2.6.14 patch that fixed race in send_sigqueue
> with thread exit. However, I do want to understand the code better and
> experiment with it some more before implementing signal handler
> unsharing. If deemed ok, it would be easy to add that functionality.
yes, it would be preferrable to have them all at once, once it hits
upstream. Also, would unsharing the thread group make sense?
Ingo
next prev parent reply other threads:[~2005-12-13 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 2:59 [PATCH -mm 0/9] unshare system call (take 3) JANAK DESAI
2005-12-13 11:20 ` Ingo Molnar [this message]
2005-12-13 14: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=20051213112029.GA14653@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=dwmw2@infradead.org \
--cc=jamie@shareable.org \
--cc=janak@us.ibm.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--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