public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: paulmck@linux.vnet.ibm.com, shemminger@vyatta.com,
	Valdis.Kletnieks@vt.edu, akpm@linux-foundation.org,
	peterz@infradead.org, kaber@trash.net,
	linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] net: if6_get_next() fix
Date: Mon, 03 May 2010 22:13:55 +0200	[thread overview]
Message-ID: <1272917635.2407.106.camel@edumazet-laptop> (raw)
In-Reply-To: <20100503.130902.172620141.davem@davemloft.net>

Le lundi 03 mai 2010 à 13:09 -0700, David Miller a écrit :
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Mon, 03 May 2010 21:46:47 +0200
> 
> > Then, net-next-2.6 doesnt yet have your commit Paul to relax
> > hlist_for_each_entry_rcu(), so its a bit difficult to continue the work.
> 
> Is that in Linus's tree yet?  If it propagates there I can make it
> propagate to net-next-2.6, you just have to tell me you need it.


Hmm, it seems it's already in net-next-2.6, sorry for the confusion.

commit 3120438ad68601f341e61e7cb1323b0e1a6ca367
Author: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Date:   Mon Feb 22 17:04:48 2010 -0800

    rcu: Disable lockdep checking in RCU list-traversal primitives
    
    The theory is that use of bare rcu_dereference() is more prone
    to error than use of the RCU list-traversal primitives.
    Therefore, disable lockdep RCU read-side critical-section
    checking in these primitives for the time being.  Once all of
    the rcu_dereference() uses have been dealt with, it may be time
    to re-enable lockdep checking for the RCU list-traversal
    primitives.
    


--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-05-03 20:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201004290021.o3T0L04Y028017@imap1.linux-foundation.org>
2010-05-02 17:46 ` mmotm 2010-04-28 - RCU whinges Valdis.Kletnieks
2010-05-03  5:38   ` Eric Dumazet
2010-05-03  5:41     ` Eric Dumazet
2010-05-03  5:43       ` Eric Dumazet
2010-05-03  5:55         ` David Miller
2010-05-10 15:40           ` Patrick McHardy
2010-05-10 15:56             ` Eric Dumazet
2010-05-10 15:57               ` Eric Dumazet
2010-05-10 16:03               ` Patrick McHardy
2010-05-10 16:04                 ` Patrick McHardy
2010-05-10 15:57             ` Paul E. McKenney
2010-05-10 16:12             ` David Miller
2010-05-10 16:27               ` Patrick McHardy
2010-05-03 14:30     ` Valdis.Kletnieks
2010-05-03 14:48       ` Eric Dumazet
2010-05-03 14:58       ` Eric Dumazet
2010-05-03 15:29         ` Valdis.Kletnieks
2010-05-03 15:43           ` Paul E. McKenney
2010-05-03 16:14             ` Eric Dumazet
2010-05-03 18:16               ` Paul E. McKenney
2010-05-03 19:46                 ` [PATCH net-next-2.6] net: if6_get_next() fix Eric Dumazet
2010-05-03 20:09                   ` David Miller
2010-05-03 20:13                     ` Eric Dumazet [this message]
2010-05-03 20:24                       ` David Miller
2010-05-03 20:50                         ` Eric Dumazet
2010-05-03 22:17                           ` David Miller
2010-05-03 22:48                             ` Paul E. McKenney
2010-05-03 22:52                           ` Paul E. McKenney
2010-05-03 22:54                             ` David Miller
2010-05-10 16:53     ` mmotm 2010-04-28 - RCU whinges Patrick McHardy

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=1272917635.2407.106.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=shemminger@vyatta.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