From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: mmotm 2010-04-28 - RCU whinges
Date: Mon, 3 May 2010 08:43:57 -0700 [thread overview]
Message-ID: <20100503154357.GF2597@linux.vnet.ibm.com> (raw)
In-Reply-To: <5112.1272900590@localhost>
On Mon, May 03, 2010 at 11:29:50AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 03 May 2010 16:58:46 +0200, Eric Dumazet said:
> > Le lundi 03 mai 2010 à 10:30 -0400, Valdis.Kletnieks@vt.edu a écrit :
>
> > > [ 9.129872] net/netfilter/nf_log.c:55 invoked rcu_dereference_check() without protection!
>
> > Thanks for the report !
> >
> > [PATCH] net: nf_log RCU fixes
> >
> > nf_log_register() and nf_log_unregister() use a mutex to have exclusive
> > access to nf_logers[]. Use appropriate rcu_dereference_protected()
> > lockdep annotation.
>
> Confirming that one fixed. Now it lives a whole 36 seconds before whinging:
>
> [ 35.328729] ===================================================
> [ 35.328803] [ INFO: suspicious rcu_dereference_check() usage. ]
> [ 35.328837] ---------------------------------------------------
> [ 35.328872] net/ipv6/addrconf.c:2977 invoked rcu_dereference_check() without protection!
> [ 35.328926]
> [ 35.328927] other info that might help us debug this:
> [ 35.328928]
> [ 35.329016]
> [ 35.329016] rcu_scheduler_active = 1, debug_locks = 0
> [ 35.329089] 2 locks held by ifconfig/2680:
> [ 35.329120] #0: (&p->lock){+.+.+.}, at: [<ffffffff810f5db8>] seq_read+0x3a/0x42d
> [ 35.329217] #1: (rcu_read_lock_bh){.+....}, at: [<ffffffff814eec68>] rcu_read_lock_bh+0x0/0x35
> [ 35.329322]
> [ 35.329323] stack backtrace:
> [ 35.329380] Pid: 2680, comm: ifconfig Tainted: G W 2.6.34-rc5-mmotm0428 #3
> [ 35.329439] Call Trace:
> [ 35.329471] [<ffffffff81064832>] lockdep_rcu_dereference+0xaa/0xb2
> [ 35.329514] [<ffffffff814ef3ae>] if6_get_next+0x34/0x6d
> [ 35.329554] [<ffffffff814ef3f8>] if6_seq_next+0x11/0x18
> [ 35.329595] [<ffffffff810f6083>] seq_read+0x305/0x42d
> [ 35.329635] [<ffffffff810f5d7e>] ? seq_read+0x0/0x42d
> [ 35.329676] [<ffffffff81129e8c>] proc_reg_read+0x8d/0xac
> [ 35.329717] [<ffffffff810db7e0>] vfs_read+0xe0/0x140
> [ 35.329758] [<ffffffff810db8f6>] sys_read+0x45/0x69
> [ 35.329799] [<ffffffff810025eb>] system_call_fastpath+0x16/0x1b
>
> Maybe I need to go and stick the "RCU whinge multiple times" patch on this
> kernel and get it over with. :)
Highly recommended. ;-)
And thanks to you for your testing efforts and to Eric for the fixes!!!
Thanx, Paul
--
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
WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Valdis.Kletnieks@vt.edu
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: mmotm 2010-04-28 - RCU whinges
Date: Mon, 3 May 2010 08:43:57 -0700 [thread overview]
Message-ID: <20100503154357.GF2597@linux.vnet.ibm.com> (raw)
In-Reply-To: <5112.1272900590@localhost>
On Mon, May 03, 2010 at 11:29:50AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 03 May 2010 16:58:46 +0200, Eric Dumazet said:
> > Le lundi 03 mai 2010 à 10:30 -0400, Valdis.Kletnieks@vt.edu a écrit :
>
> > > [ 9.129872] net/netfilter/nf_log.c:55 invoked rcu_dereference_check() without protection!
>
> > Thanks for the report !
> >
> > [PATCH] net: nf_log RCU fixes
> >
> > nf_log_register() and nf_log_unregister() use a mutex to have exclusive
> > access to nf_logers[]. Use appropriate rcu_dereference_protected()
> > lockdep annotation.
>
> Confirming that one fixed. Now it lives a whole 36 seconds before whinging:
>
> [ 35.328729] ===================================================
> [ 35.328803] [ INFO: suspicious rcu_dereference_check() usage. ]
> [ 35.328837] ---------------------------------------------------
> [ 35.328872] net/ipv6/addrconf.c:2977 invoked rcu_dereference_check() without protection!
> [ 35.328926]
> [ 35.328927] other info that might help us debug this:
> [ 35.328928]
> [ 35.329016]
> [ 35.329016] rcu_scheduler_active = 1, debug_locks = 0
> [ 35.329089] 2 locks held by ifconfig/2680:
> [ 35.329120] #0: (&p->lock){+.+.+.}, at: [<ffffffff810f5db8>] seq_read+0x3a/0x42d
> [ 35.329217] #1: (rcu_read_lock_bh){.+....}, at: [<ffffffff814eec68>] rcu_read_lock_bh+0x0/0x35
> [ 35.329322]
> [ 35.329323] stack backtrace:
> [ 35.329380] Pid: 2680, comm: ifconfig Tainted: G W 2.6.34-rc5-mmotm0428 #3
> [ 35.329439] Call Trace:
> [ 35.329471] [<ffffffff81064832>] lockdep_rcu_dereference+0xaa/0xb2
> [ 35.329514] [<ffffffff814ef3ae>] if6_get_next+0x34/0x6d
> [ 35.329554] [<ffffffff814ef3f8>] if6_seq_next+0x11/0x18
> [ 35.329595] [<ffffffff810f6083>] seq_read+0x305/0x42d
> [ 35.329635] [<ffffffff810f5d7e>] ? seq_read+0x0/0x42d
> [ 35.329676] [<ffffffff81129e8c>] proc_reg_read+0x8d/0xac
> [ 35.329717] [<ffffffff810db7e0>] vfs_read+0xe0/0x140
> [ 35.329758] [<ffffffff810db8f6>] sys_read+0x45/0x69
> [ 35.329799] [<ffffffff810025eb>] system_call_fastpath+0x16/0x1b
>
> Maybe I need to go and stick the "RCU whinge multiple times" patch on this
> kernel and get it over with. :)
Highly recommended. ;-)
And thanks to you for your testing efforts and to Eric for the fixes!!!
Thanx, Paul
next prev parent reply other threads:[~2010-05-03 15:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 23:53 mmotm 2010-04-28-16-53 uploaded akpm
2010-04-29 21:32 ` Valdis.Kletnieks
2010-04-29 21:53 ` Andrew Morton
2010-04-29 22:00 ` Andrew Morton
2010-04-30 12:11 ` Lee Schermerhorn
2010-04-30 18:02 ` Lee Schermerhorn
2010-04-30 18:47 ` Valdis.Kletnieks
2010-04-30 19:05 ` Lee Schermerhorn
2010-05-02 17:38 ` mmotm 2010-04-28 - nouveau driver issues Valdis.Kletnieks
2010-05-02 17:38 ` Valdis.Kletnieks
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:41 ` Eric Dumazet
2010-05-03 5:43 ` 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:03 ` Patrick McHardy
2010-05-10 16:04 ` 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: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 [this message]
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 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
2010-05-03 20:13 ` Eric Dumazet
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=20100503154357.GF2597@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=peterz@infradead.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.