diff options
| author | Ewan D. Milne <[email protected]> | 2019-01-17 16:14:45 +0000 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2019-01-23 01:40:59 +0000 |
| commit | c41f59884be5cca293ed61f3d64637dbba3a6381 (patch) | |
| tree | f438ad4606805b8987231877def62d5d15ed5a50 /lib/xarray.c | |
| parent | scsi: lpfc: nvme: avoid hang / use-after-free when destroying localport (diff) | |
| download | kernel-c41f59884be5cca293ed61f3d64637dbba3a6381.tar.gz kernel-c41f59884be5cca293ed61f3d64637dbba3a6381.zip | |
scsi: lpfc: nvmet: avoid hang / use-after-free when destroying targetport
We cannot wait on a completion object in the lpfc_nvme_targetport structure
in the _destroy_targetport() code path because the NVMe/fc transport will
free that structure immediately after the .targetport_delete() callback.
This results in a use-after-free, and a hang if slub_debug=FZPU is enabled.
Fix this by putting the completion on the stack.
Signed-off-by: Ewan D. Milne <[email protected]>
Acked-by: James Smart <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'lib/xarray.c')
0 files changed, 0 insertions, 0 deletions