diff options
| author | Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> | 2007-03-24 12:52:16 -0700 |
|---|---|---|
| committer | David S. Miller <davem@sunset.davemloft.net> | 2007-03-25 18:48:01 -0700 |
| commit | ecbb416939da77c0d107409976499724baddce7b (patch) | |
| tree | 313f786f9f4d5fec3f016c292dea1705924fa9b6 /lib/debug_locks.c | |
| parent | e1701c68c1d1aeb3213d7016593ea9a1d4309417 (diff) | |
| download | op-kernel-dev-ecbb416939da77c0d107409976499724baddce7b.zip op-kernel-dev-ecbb416939da77c0d107409976499724baddce7b.tar.gz | |
[NET]: Fix neighbour destructor handling.
->neigh_destructor() is killed (not used), replaced with
->neigh_cleanup(), which is called when neighbor entry goes to dead
state. At this point everything is still valid: neigh->dev,
neigh->parms etc.
The device should guarantee that dead neighbor entries (neigh->dead !=
0) do not get private part initialized, otherwise nobody will cleanup
it.
I think this is enough for ipoib which is the only user of this thing.
Initialization private part of neighbor entries happens in ipib
start_xmit routine, which is not reached when device is down. But it
would be better to add explicit test for neigh->dead in any case.
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/debug_locks.c')
0 files changed, 0 insertions, 0 deletions
