From: Oleg Nesterov <oleg@tv-sign.ru>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Paul Menage <menage@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
serue@us.ibm.com, penberg@cs.helsinki.fi,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [-mm] Add an owner to the mm_struct (v9)]
Date: Thu, 17 Apr 2008 21:08:44 +0400 [thread overview]
Message-ID: <20080417170844.GA5575@tv-sign.ru> (raw)
In-Reply-To: <48078B9B.9070508@linux.vnet.ibm.com>
On 04/17, Balbir Singh wrote:
>
> Oleg Nesterov wrote:
> >> CLONE_THREAD without CLONE_VM when creating a new subthread.
> >
> > No, no, this is not possible/allowed.
> >
> > Please look at copy_process, CLONE_THREAD requires CLONE_SIGHAND,
> > CLONE_SIGHAND needs CLONE_VM.
> >
>
> What about the other way round, CLONE_VM without CLONE_THREAD?
Yes, this is possible, and this is why mm_update_next_owner() has to be so
complicated. The same for zap_threads/elf_core_dump.
If only I knew why we allow CLONE_VM! except for CLONE_THREAD/CLONE_VFORK
of course, but there are trivial.
And thanks to you and Paul for your explanations.
Oleg.
next prev parent reply other threads:[~2008-04-17 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 14:13 Balbir Singh
2008-04-14 14:49 ` Pekka Enberg
2008-04-14 16:04 ` Paul Menage
2008-04-14 19:36 ` Andrew Morton
2008-04-14 21:06 ` Pekka Enberg
2008-04-15 0:07 ` Andrew Morton
2008-04-15 17:13 ` Oleg Nesterov
2008-04-15 18:13 ` Paul Menage
2008-04-15 19:59 ` Oleg Nesterov
2008-04-17 3:38 ` Balbir Singh
2008-04-17 11:30 ` Oleg Nesterov
2008-04-17 16:34 ` Paul Menage
2008-04-17 16:19 ` Oleg Nesterov
2008-04-17 17:40 ` Balbir Singh
2008-04-17 17:08 ` Oleg Nesterov [this message]
2008-04-17 17:50 ` Paul Menage
2008-04-17 19:07 ` Balbir Singh
2008-04-17 17:49 ` Paul Menage
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=20080417170844.GA5575@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=penberg@cs.helsinki.fi \
--cc=serue@us.ibm.com \
/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®