summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/calxeda
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2013-05-09 12:28:16 +0200
committerDavid S. Miller <davem@davemloft.net>2013-05-12 01:26:38 +0200
commitf77d602124d865c38705df7fa25c03de9c284ad2 (patch)
tree173c11c4c8bfe13a891dcee6bf546c2bc4c9ed76 /drivers/net/ethernet/calxeda
parentmacvlan: fix passthru mode race between dev removal and rx path (diff)
downloadlinux-f77d602124d865c38705df7fa25c03de9c284ad2.tar.xz
linux-f77d602124d865c38705df7fa25c03de9c284ad2.zip
ipv6: do not clear pinet6 field
We have seen multiple NULL dereferences in __inet6_lookup_established() After analysis, I found that inet6_sk() could be NULL while the check for sk_family == AF_INET6 was true. Bug was added in linux-2.6.29 when RCU lookups were introduced in UDP and TCP stacks. Once an IPv6 socket, using SLAB_DESTROY_BY_RCU is inserted in a hash table, we no longer can clear pinet6 field. This patch extends logic used in commit fcbdf09d9652c891 ("net: fix nulls list corruptions in sk_prot_alloc") TCP/UDP/UDPLite IPv6 protocols provide their own .clear_sk() method to make sure we do not clear pinet6 field. At socket clone phase, we do not really care, as cloning the parent (non NULL) pinet6 is not adding a fatal race. Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/calxeda')
0 files changed, 0 insertions, 0 deletions