On Fri, 6 Nov 2020 11:33:17 -0800, Lee Duncan wrote:
> iSCSI NOPs are sometimes "lost", mistakenly sent to the
> user-land iscsid daemon instead of handled in the kernel,
> as they should be, resulting in a message from the daemon like:
>
> > iscsid: Got nop in, but kernel supports nop handling.
>
> This can occur because of the new forward- and back-locks,
> and the fact that an iSCSI NOP response can occur before
> processing of the NOP send is complete. This can result
> in "conn->ping_task" being NULL in iscsi_nop_out_rsp(),
> when the pointer is actually in the process of being set.
>
> [...]
Applied to 5.10/scsi-fixes, thanks!
[1/1] scsi: libiscsi: Fix NOP race condition
https://git.kernel.org/mkp/scsi/c/fe0a8a95e713
--
Martin K. Petersen Oracle Linux Engineering
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/open-iscsi/160559316816.969.2361617121962261448.b4-ty%40oracle.com.
