IB/mlx5: Avoid async events on invalid port number
On a single ported Connect-IB, its possible for the firmware to issue events on the non-existing 2nd port. Make sure to ignore events generated for such ports. Signed-off-by: Eli Cohen <eli@mellanox.com> Signed-off-by: Roland Dreier <roland@purestorage.com>
This commit is contained in:
parent
203099fd73
commit
a0c84c326f
|
@ -1006,6 +1006,11 @@ static void mlx5_ib_event(struct mlx5_core_dev *dev, enum mlx5_dev_event event,
|
||||||
ibev.device = &ibdev->ib_dev;
|
ibev.device = &ibdev->ib_dev;
|
||||||
ibev.element.port_num = port;
|
ibev.element.port_num = port;
|
||||||
|
|
||||||
|
if (port < 1 || port > ibdev->num_ports) {
|
||||||
|
mlx5_ib_warn(ibdev, "warning: event on port %d\n", port);
|
||||||
|
return;
|
||||||
|
}
|
||||||
|
|
||||||
if (ibdev->ib_active)
|
if (ibdev->ib_active)
|
||||||
ib_dispatch_event(&ibev);
|
ib_dispatch_event(&ibev);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue