On 11/10/2017 02:08 AM, James Smart wrote:
> When the driver is unloading, the nvme transport could be in the
> process of submitting new requests, will send abort requests to
> terminate associations, or may make LS-related requests.
> The driver's abort and request entry points currently is ignorant
> of the unloading state and is starting the requests even though
> the infrastructure to complete them continues to teardown.
> 
> Change the entry points for new requests to check whether unloading
> and if so, reject the requests. Abort routines check unloading, and
> if so, noop the request. An abort is noop'd as the teardown paths
> are already aborting/terminating the io outstanding at the time the
> teardown initiated.
> 
> Signed-off-by: Dick Kennedy <dick.kenn...@broadcom.com>
> Signed-off-by: James Smart <james.sm...@broadcom.com>
> ---
>  drivers/scsi/lpfc/lpfc_nvme.c  | 14 ++++++++++++++
>  drivers/scsi/lpfc/lpfc_nvmet.c | 11 +++++++++++
>  2 files changed, 25 insertions(+)
> 
Reviewed-by: Hannes Reinecke <h...@suse.com>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Teamlead Storage & Networking
h...@suse.de                                   +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

Reply via email to