On Thu, 2020-10-01 at 12:21 -0700, David Miller wrote:
> From: sa...@kernel.org
> Date: Wed, 30 Sep 2020 19:05:02 -0700
>
> > @@ -201,6 +206,9 @@ void mlx5_enter_error_state(struct
> mlx5_core_dev *dev, bool force)
> > err_detected = true;
> > }
> > mutex_lock(&dev->intf_
From: sa...@kernel.org
Date: Wed, 30 Sep 2020 19:05:02 -0700
> @@ -201,6 +206,9 @@ void mlx5_enter_error_state(struct mlx5_core_dev *dev,
> bool force)
> err_detected = true;
> }
> mutex_lock(&dev->intf_state_mutex);
> + if (!mlx5_is_device_initialized(dev))
> +
From: Shay Drory
On error flow due to failure on driver load, driver can be
un-initializing while a health work is running in the background,
health work shouldn't be allowed at this point, as it needs resources to
be initialized and there is no point to recover on driver load failures.
Therefor
