[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.WNT.2.00.1111291600220.228@TSI>
Date: Tue, 29 Nov 2011 16:03:42 -0700 (Mountain Standard Time)
From: Marc Aurele La France <tsi@...berta.ca>
To: Eric Dumazet <eric.dumazet@...il.com>
cc: Roland Dreier <roland@...nel.org>,
David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org
Subject: Re: RCU'ed dst_get_neighbour()
On Tue, 29 Nov 2011, Eric Dumazet wrote:
> Le mardi 29 novembre 2011 à 15:32 -0700, Marc Aurele La France a écrit :
>> But your audit is incomplete, a grep of 3.1.3 for dst_get_neighbour() and
>> dst_get_neighbour_raw() reveals occurrences in ...
>> include/net/dst.h
>> net/atm/clip.c
>> net/sched/sch_teql.c
>> net/core/neighbour.c
>> net/ipv4/ip_gre.c
>> net/ipv4/ip_output.c
>> net/ipv4/route.c
>> net/xfrm/xfrm_policy.c
>> net/bridge/br_netfilter.c
>> net/decnet/dn_neigh.c
>> net/decnet/dn_route.c
>> net/ipv6/sit.c
>> net/ipv6/addrconf.c
>> net/ipv6/route.c
>> net/ipv6/ndisc.c
>> net/ipv6/ip6_output.c
>> net/ipv6/ip6_fib.c
> All these are already covered, or else bad things would already
> happened.
No, only warnings (splats as you call them) would be produced. The fact
is you added side-effects to dst_get_neighbour(), and I would expect all
its invocations to be affected.
Marc.
+----------------------------------+----------------------------------+
| Marc Aurele La France | work: 1-780-492-9310 |
| Academic Information and | fax: 1-780-492-1729 |
| Communications Technologies | email: tsi@...berta.ca |
| 352 General Services Building +----------------------------------+
| University of Alberta | |
| Edmonton, Alberta | Standard disclaimers apply |
| T6G 2H1 | |
| CANADA | |
+----------------------------------+----------------------------------+
Powered by blists - more mailing lists