Jack Morgenstein bffb023ad2 net/mlx4_core: Fix GEN_EQE accessing uninitialixed mutex
We occasionally see in procedure mlx4_GEN_EQE that the driver tries
to grab an uninitialized mutex.

This can occur in only one of two ways:
1. We are trying to generate an async event on an uninitialized slave.
2. We are trying to generate an async event on an illegal slave number
   ( < 0 or > persist->num_vfs) or an inactive slave.

To deal with #1: move the mutex initialization from specific slave init
sequence in procedure mlx_master_do_cmd to mlx4_multi_func_init() (so that
the mutex is always initialized for all slaves).

To deal with #2: check in procedure mlx4_GEN_EQE that the slave number
provided is in the proper range and that the slave is active.

Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2015-03-24 15:22:52 -04:00
..
2015-03-02 12:08:43 -05:00
2015-03-17 10:41:26 -07:00
2015-02-17 09:27:54 -08:00
2015-02-15 10:48:44 -08:00
2015-02-03 15:48:51 -08:00
2015-03-22 16:38:19 -07:00
2015-02-03 15:58:39 -08:00
2015-02-18 09:05:48 -08:00
2015-02-04 09:15:18 +01:00
2015-03-12 09:45:46 -07:00
2015-02-18 08:40:29 +01:00
2015-02-17 09:38:59 -08:00
2015-03-22 11:33:55 -07:00
2015-02-15 10:24:55 -08:00
2015-02-03 15:58:39 -08:00