diff options
author | James Smart <jsmart2021@gmail.com> | 2017-11-20 16:00:41 -0800 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2017-12-04 20:32:55 -0500 |
commit | 3386f4bdd243ad5a9094d390297602543abe9902 (patch) | |
tree | a547858cbaca4660fd4917ea0997f674eebb07d1 /certs | |
parent | add9d6be3d650bf897b1c3feadabcf42e216acdb (diff) | |
download | op-kernel-dev-3386f4bdd243ad5a9094d390297602543abe9902.zip op-kernel-dev-3386f4bdd243ad5a9094d390297602543abe9902.tar.gz |
scsi: lpfc: Fix crash during driver unload with running nvme traffic
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.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions