diff options
| author | James Smart <jsmart2021@gmail.com> | 2018-11-30 03:09:39 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2018-12-08 06:35:33 +0300 |
| commit | 1165a5c2206cf8e4811caab145d16a8d87c69111 (patch) | |
| tree | 0c28d57e34a1a1bd88edfd1252671b369305966e /crypto/ofb.c | |
| parent | 76558b25733140a0c6bd53ea8af04b2811c92ec3 (diff) | |
| download | linux-1165a5c2206cf8e4811caab145d16a8d87c69111.tar.xz | |
scsi: lpfc: Fix driver release of fw-logging buffers
On driver termination, after the driver stops fw logging by writing a
register on the chip, the driver immediately unmaps and frees the logging
buffer, without confirming in any way that the chip has received the write
and terminated the logging. As termination on the chip is not immediate,
the chip may issue a dma request to the now unmapped dma buffer, resulting
in a iommu fault.
Change the driver to receive a confirmation that logging ahs been
terminated. As the driver always issues an SLI reset with the device as
part of shutdown, and as part of that is receiving confirmation that the
reset is complete - the driver was modified to perform the write to disable
fw logging prior to the SLI reset and only free the fw log buffer after the
SLI reset is complete. That guarantees use of the fw log buffer is fully
terminated when it is unmapped.
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'crypto/ofb.c')
0 files changed, 0 insertions, 0 deletions