On 12/7/23 11:42 AM, lduncan@xxxxxxxx wrote:
From: Lee Duncan <lduncan@xxxxxxxx> The LIO target code has a warning about setting the read and/or write header bits with a PDU that has zero transfer length, even though the code mentions that the SPEC (RFC 3720) allows this, and that some initiators set these bits. But in practice such initiators end up flooding the logs with thousands of warning messages for IO that is allowed.
I've never seen us hit this. What initiator is doing this and what is the command they are sending?
Is it also related to the first patch? Is some initiator sending something like a TUR with the immediate bit set during some sort of stall/timeout?
