diff options
| author | Ido Schimmel <idosch@mellanox.com> | 2017-02-06 16:20:16 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-02-06 11:25:57 -0500 |
| commit | 01b1aa359dd481579de6047af8d7874e6e529585 (patch) | |
| tree | a83784f678946263f0792eae3f06ce9d7272f91a /include/dt-bindings/reset/qcom,gcc-msm8960.h | |
| parent | 8a0b7275268504259cc1a17bae839d23c4f6e2bc (diff) | |
mlxsw: spectrum_router: Don't read 'nud_state' without lock
We periodically ask the neighbouring system to try and resolve
neighbours that are used for nexthops, but aren't currently resolved.
However, 'nud_state' is protected by the neighbour lock, so we shouldn't
access it without taking it. Instead, we can simply check the
'connected' field of the neighbour entry, which we update upon
NEIGH_UPDATE events.
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/dt-bindings/reset/qcom,gcc-msm8960.h')
0 files changed, 0 insertions, 0 deletions