All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] futex_find_get_task: don't take tasklist_lock
Date: Tue, 22 Aug 2006 12:44:46 +0200	[thread overview]
Message-ID: <20060822104446.GB28183@elte.hu> (raw)
In-Reply-To: <20060821170621.GA1643@oleg>


* Oleg Nesterov <oleg@tv-sign.ru> wrote:

> It is ok to do find_task_by_pid() + get_task_struct() under 
> rcu_read_lock(), we cand drop tasklist_lock.
> 
> Note that testing of ->exit_state is racy with or without tasklist 
> anyway.
> 
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>

yeah. (We did this in the -rt tree for some time too, never saw any 
problems.)

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

      reply	other threads:[~2006-08-22 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 17:06 [PATCH 2/3] futex_find_get_task: don't take tasklist_lock Oleg Nesterov
2006-08-22 10:44 ` Ingo Molnar [this message]

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=20060822104446.GB28183@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.