aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorIdo Schimmel <[email protected]>2016-12-23 08:32:48 +0000
committerDavid S. Miller <[email protected]>2016-12-23 17:31:18 +0000
commit53f800e3baf980827c197a9332f63effe80d4809 (patch)
tree3d8d3150504942fc2db94e99de6b5b665414c45f /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
parentipv6: handle -EFAULT from skb_copy_bits (diff)
downloadkernel-53f800e3baf980827c197a9332f63effe80d4809.tar.gz
kernel-53f800e3baf980827c197a9332f63effe80d4809.zip
neigh: Send netevent after marking neigh as dead
neigh_cleanup_and_release() is always called after marking a neighbour as dead, but it only notifies user space and not in-kernel listeners of the netevent notification chain. This can cause multiple problems. In my specific use case, it causes the listener (a switch driver capable of L3 offloads) to believe a neighbour entry is still valid, and is thus erroneously kept in the device's table. Fix that by sending a netevent after marking the neighbour as dead. Fixes: a6bf9e933daf ("mlxsw: spectrum_router: Offload neighbours based on NUD state change") Signed-off-by: Ido Schimmel <[email protected]> Signed-off-by: Jiri Pirko <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions