All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: paulmck@linux.vnet.ibm.com, yoshfuji@linux-ipv6.org,
	netdev@vger.kernel.org, mingo@elte.hu, akpm@linux-foundation.org
Subject: Re: What protects rcu_dereference() in __in6_dev_get()?
Date: Fri, 15 Jan 2010 16:31:36 +0100	[thread overview]
Message-ID: <1263569496.4244.436.camel@laptop> (raw)
In-Reply-To: <4B5089CA.2050202@gmail.com>

On Fri, 2010-01-15 at 16:29 +0100, Eric Dumazet wrote:

> I guess so, but is lockdep_is_held(&mutex) actually cheking this mutex is owned by us ?

Yep, assuming lockdep is still functional, otherwise its return value
will be undefined.


  reply	other threads:[~2010-01-15 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 18:32 What protects rcu_dereference() in __in6_dev_get()? Paul E. McKenney
2010-01-15  5:50 ` Eric Dumazet
2010-01-15 15:15   ` Paul E. McKenney
2010-01-15 15:29     ` Eric Dumazet
2010-01-15 15:31       ` Peter Zijlstra [this message]
2010-01-15 15:53       ` Paul E. McKenney

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=1263569496.4244.436.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=eric.dumazet@gmail.com \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=yoshfuji@linux-ipv6.org \
    /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.