diff options
| author | James Smart <[email protected]> | 2021-10-20 21:14:16 +0000 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2021-10-21 03:33:46 +0000 |
| commit | af984c87293b19dccbd0b16afc57c5c9a4a279c7 (patch) | |
| tree | 3c1ab333dbcece2368161c75758097ca57deeb9a /fs/ext4/fast_commit.c | |
| parent | scsi: lpfc: Fix link down processing to address NULL pointer dereference (diff) | |
| download | kernel-af984c87293b19dccbd0b16afc57c5c9a4a279c7.tar.gz kernel-af984c87293b19dccbd0b16afc57c5c9a4a279c7.zip | |
scsi: lpfc: Allow fabric node recovery if recovery is in progress before devloss
A link bounce to a slow fabric may observe FDISC response delays lasting
longer than devloss tmo. Current logic decrements the final fabric node
kref during a devloss tmo event. This results in a NULL ptr dereference
crash if the FDISC completes for that fabric node after devloss tmo.
Fix by adding the NLP_IN_RECOV_POST_DEV_LOSS flag, which is set when
devloss tmo triggers and we've noticed that fabric node recovery has
already started or finished in between the time lpfc_dev_loss_tmo_callbk
queues lpfc_dev_loss_tmo_handler. If fabric node recovery succeeds, then
the driver reverses the devloss tmo marked kref put with a kref get. If
fabric node recovery fails, then the final kref put relies on the ELS
timing out or the REG_LOGIN cmpl routine.
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 'fs/ext4/fast_commit.c')
0 files changed, 0 insertions, 0 deletions