| commit | 4ae289444b968b4cefd776ada8da519ce10e56fa | |
| author | Pavel Emelyanov <xemul@openvz.org> | |
| Mon, 15 Oct 2007 19:54:15 +0000 (15 12:54 -0700) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Mon, 15 Oct 2007 19:54:15 +0000 (15 12:54 -0700) | ||
| tree | 06aa4ff04bb1acdb64c29fc4b28a5cf91b1d57b8 | treesnapshot (tar.gz zip) |
| parent | f1673ca52c04f1b311abe03fd67cd4d650d19435 | commitdiff |
[NEIGH]: Ensure that pneigh_lookup is protected with RTNL
The pnigh_lookup is used to lookup proxy entries and to
create them in case lookup failed.
However, the "creation" code does not perform the re-lookup
after GFP_KERNEL allocation. This is done because the code
is expected to be protected with the RTNL lock, so add the
assertion (mainly to address future questions from new network
developers like me :) ).
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
The pnigh_lookup is used to lookup proxy entries and to
create them in case lookup failed.
However, the "creation" code does not perform the re-lookup
after GFP_KERNEL allocation. This is done because the code
is expected to be protected with the RTNL lock, so add the
assertion (mainly to address future questions from new network
developers like me :) ).
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/core/neighbour.c | diffblobblamehistory |