diff options
author | Mark Zhang | 2018-12-05 14:50:49 +0100 |
---|---|---|
committer | Greg Kroah-Hartman | 2019-01-13 09:50:57 +0100 |
commit | 8c9c3747750a5d8fe217a51d026f3d2c0a4771ae (patch) | |
tree | ca4742ff4f2c82dce0160fcf67af07778081b4ee /scripts | |
parent | drm/amdgpu: Fix DEBUG_LOCKS_WARN_ON(depth <= 0) in amdgpu_ctx.lock (diff) | |
download | kernel-qcow2-linux-8c9c3747750a5d8fe217a51d026f3d2c0a4771ae.tar.gz kernel-qcow2-linux-8c9c3747750a5d8fe217a51d026f3d2c0a4771ae.tar.xz kernel-qcow2-linux-8c9c3747750a5d8fe217a51d026f3d2c0a4771ae.zip |
IB/core: Fix oops in netdev_next_upper_dev_rcu()
[ Upstream commit 37fbd834b4e492dc41743830cbe435f35120abd8 ]
When support for bonding of RoCE devices was added, there was
necessarily a link between the RoCE device and the paired netdevice that
was part of the bond. If you remove the mlx4_en module, that paired
association is broken (the RoCE device is still present but the paired
netdevice has been released). We need to account for this in
is_upper_ndev_bond_master_filter() and filter out those links with a
broken pairing or else we later oops in netdev_next_upper_dev_rcu().
Fixes: 408f1242d940 ("IB/core: Delete lower netdevice default GID entries in bonding scenario")
Signed-off-by: Mark Zhang <markz@mellanox.com>
Reviewed-by: Parav Pandit <parav@mellanox.com>
Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions