From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] sched: add __rcu annotation
Date: Tue, 04 Jan 2011 12:01:24 +0100 [thread overview]
Message-ID: <1294138884.2016.106.camel@laptop> (raw)
In-Reply-To: <1294138545.3579.53.camel@edumazet-laptop>
On Tue, 2011-01-04 at 11:55 +0100, Eric Dumazet wrote:
> Le mardi 04 janvier 2011 à 11:17 +0100, Peter Zijlstra a écrit :
>
> > I'm really starting to detest sparse (lock annotations), it keeps adding
> > these annotations, but does it ever catch an actual bug?
>
> Actually I caught at least one bug in networking (FIB code ?) thanks to
> these __rcu annotations ;)
>
> Cannot remember the exact bug, sorry ;)
Ah, ok.. then they're not completely pointless. Lai, can you resend with
a slightly better changelog?
prev parent reply other threads:[~2011-01-04 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 8:06 [PATCH 1/3] sched: add __rcu annotation Lai Jiangshan
2011-01-04 10:17 ` Peter Zijlstra
2011-01-04 10:55 ` Eric Dumazet
2011-01-04 11:01 ` Peter Zijlstra [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=1294138884.2016.106.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=arnd@arndb.de \
--cc=eric.dumazet@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.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