mlx4_core: Initialize ctx_list and ctx_lock earlier
commitb581401ed0cc83a4483ed39c00a14a60bacecc3a
authorRoland Dreier <rolandd@cisco.com>
Thu, 7 Jun 2007 18:51:58 +0000 (7 11:51 -0700)
committerRoland Dreier <rolandd@cisco.com>
Thu, 7 Jun 2007 18:51:58 +0000 (7 11:51 -0700)
treefa83991f1f429c0bf9876856d5255cf4a8be79fe
parent09360d5408cb641abff0f32a172a3332f02e8e88
mlx4_core: Initialize ctx_list and ctx_lock earlier

We may call mlx4_dispatch_event() before mlx4_register_device() is
called for a device, because for example a catastrophic error happens
immediately after we enable interrupts.  Therefore priv->ctx_list and
priv->ctx_lock need to be initialized earlier.

This bug was actually exposed by the MSI-X bug that returned IRQ numbers
to drivers in reverse order, so that the first FW command
interrupt looked to mlx4 like a catastrophic error.

Signed-off-by: Roland Dreier <rolandd@cisco.com>
drivers/net/mlx4/intf.c
drivers/net/mlx4/main.c