diff options
| author | James Smart <[email protected]> | 2021-07-07 11:43:47 -0700 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2021-07-18 22:30:37 -0400 |
| commit | c65436b21c3abbdaacd9c9f68bf2fa94e103168d (patch) | |
| tree | 05a1b8705d2e2fcf1e26d563a0939eddf5339f9d /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 0614568361b0c1827f999b1fff21223a496c740b (diff) | |
scsi: lpfc: Call discovery state machine when handling PLOGI/ADISC completions
In the PLOGI and ADISC completion handling, the device removal event could
be skipped during some link errors. This could leave a stale node in UNUSED
state. Driver unload would hang for a long time waiting for this node to
be freed.
Resolve by taking the following steps:
- Always post ADISC completion events to discovery state machine upon
ADISC completion.
- In case of a completion error for PLOGI/ADISC, ensure that init refcount
is dropped if not registered with transport.
Link: https://lore.kernel.org/r/[email protected]
Co-developed-by: Justin Tee <[email protected]>
Signed-off-by: Justin Tee <[email protected]>
Signed-off-by: James Smart <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions