From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: roy.qing.li@gmail.com, ari.m.savolainen@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] neigh: fix rcu splat in neigh_update()
Date: Wed, 19 Oct 2011 19:39:10 -0400 (EDT) [thread overview]
Message-ID: <20111019.193910.388701305423765916.davem@davemloft.net> (raw)
In-Reply-To: <1318929095.2657.19.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 18 Oct 2011 11:11:35 +0200
> Le mardi 18 octobre 2011 à 16:32 +0800, roy.qing.li@gmail.com a écrit :
>> when use dst_get_neighbour to get neighbour, we need
>> rcu_read_lock to protect, since dst_get_neighbour uses
>> rcu_dereference.
>>
>> The bug was reported by Ari Savolainen <ari.m.savolainen@gmail.com>
>>
> ...
>>
>> Reported-by: Ari Savolainen <ari.m.savolainen@gmail.com>
>> Signed-off-by: RongQing <roy.qing.li@gmail.com>
>
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2011-10-19 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 8:32 [PATCH net-next] neigh: fix rcu splat in neigh_update() roy.qing.li
2011-10-18 9:11 ` Eric Dumazet
2011-10-19 23:39 ` David Miller [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=20111019.193910.388701305423765916.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ari.m.savolainen@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@gmail.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;
as well as URLs for NNTP newsgroup(s).