public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: dhowells@redhat.com, jmorris@namei.org, roland@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rework/fix is_single_threaded()
Date: Mon, 22 Jun 2009 14:04:40 -0700	[thread overview]
Message-ID: <20090622140440.01d85542.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090622171431.GA5010@redhat.com>

On Mon, 22 Jun 2009 19:14:31 +0200
Oleg Nesterov <oleg@redhat.com> wrote:

> On 06/22, Andrew Morton wrote:
> >
> > hm, that's still all a bit marginal/waffly.
> >
> > >
> > > > From: Oleg Nesterov <oleg@redhat.com>
> > > >
> > > > - Fix the comment, is_single_threaded(p) actually means that nobody shares
> > > >   ->mm with p.
> > > >
> > > >   I think this helper should be renamed, and it should not have arguments.
> > > >   With or without this patch it must not be used unless p == current,
> > > >   otherwise we can't safely use p->signal or p->mm.
> > > >
> > > > - "if (atomic_read(&p->signal->count) != 1)" is not right when we have a
> > > >   zombie group leader, use signal->live instead.
> > > >
> > > > - Add PF_KTHREAD check to skip kernel threads which may borrow p->mm,
> > > >   otherwise we can return the wrong "false".
> > > >
> > > > - Use for_each_process() instead of do_each_thread(), all threads must use
> > > >   the same ->mm.
> > > >
> > > > - Use down_write(mm->mmap_sem) + rcu_read_lock() instead of tasklist_lock
> > > >   to iterate over the process list. If there is another CLONE_VM process
> > > >   it can't pass exit_mm() which takes the same mm->mmap_sem. We can miss
> > > >   a freshly forked CLONE_VM task, but this doesn't matter because we must
> > > >   see its parent and return false.
> >
> > Maybe we should do the locking change in a separate and subsequent
> > patch?
> 
> Sure, I can split these changes. Or we can just forget about this patch.

noooo the world needs oleg patches.

> 
> But what is the problem with this patch?

The discussion between yourself and David seems to be unresolved, so
I have it in wait-and-see mode.

> David, do you still dislike ->mmap_sem? I didn't see other objections,
> and again, imho tasklist_lock is worse.


  reply	other threads:[~2009-06-22 21:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 21:45 [PATCH] rework/fix is_single_threaded() Oleg Nesterov
2009-04-15 23:32 ` Andrew Morton
2009-04-16 13:40   ` Oleg Nesterov
2009-04-16 10:04 ` David Howells
2009-04-16 13:36   ` Oleg Nesterov
2009-04-16 14:36     ` Stephen Smalley
2009-04-16 14:54     ` Oleg Nesterov
2009-06-18 19:07       ` Andrew Morton
2009-06-18 19:42         ` Oleg Nesterov
2009-06-22 18:51           ` Andrew Morton
2009-06-22 17:14             ` Oleg Nesterov
2009-06-22 21:04               ` Andrew Morton [this message]
2009-06-22 19:24                 ` Oleg Nesterov
2009-07-09 13:01                   ` David Howells
2009-07-09 21:25                     ` Oleg Nesterov

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=20090622140440.01d85542.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=roland@redhat.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