On 10/28/19 9:38 PM, Bart Van Assche wrote:
On 10/28/19 3:57 AM, Damien Le Moal wrote:
struct scsi_cmnd cmd->req.resid_len which is returned and set
respectively by the helper functions scsi_get_resid() and
scsi_set_resid() is an unsigned int. Reflect this fact in the interface
of these helper functions.
[ ... ]
-static inline void scsi_set_resid(struct scsi_cmnd *cmd, int resid)
+static inline void scsi_set_resid(struct scsi_cmnd *cmd, unsigned int
resid)
{
cmd->req.resid_len = resid;
}
-static inline int scsi_get_resid(struct scsi_cmnd *cmd)
+static inline unsigned int scsi_get_resid(struct scsi_cmnd *cmd)
{
return cmd->req.resid_len;
}
From the iSCSI RFC:
SCSI-Presented Data Transfer Length (SPDTL) is the term this document
uses (see Section 1.1 for definition) to represent the aggregate data
length that the target SCSI layer attempts to transfer using the
local iSCSI layer for a task. Expected Data Transfer Length (EDTL)
is the iSCSI term that represents the length of data that the iSCSI
layer expects to transfer for a task. EDTL is specified in the SCSI
Command PDU.
When SPDTL = EDTL for a task, the target iSCSI layer completes the
task with no residuals. Whenever SPDTL differs from EDTL for a task,
that task is said to have a residual.
If SPDTL > EDTL for a task, iSCSI Overflow MUST be signaled in the
SCSI Response PDU as specified in [RFC3720]. The Residual Count MUST
be set to the numerical value of (SPDTL - EDTL).
If SPDTL < EDTL for a task, iSCSI Underflow MUST be signaled in the
SCSI Response PDU as specified in [RFC3720]. The Residual Count MUST
be set to the numerical value of (EDTL - SPDTL).
Note that the Overflow and Underflow scenarios are independent of
Data-In and Data-Out. Either scenario is logically possible in
either direction of data transfer.
If the residual is changed from signed into unsigned, how is a SCSI LLD
expected to report the difference between residual overflow and residual
underflow to the SCSI core?
You don't have to. To quote RFC 3720 page 122:
bit 5 - (O) set for Residual Overflow. In this case, the Residual
Count indicates the number of bytes that were not transferred
because the initiator's Expected Data Transfer Length was not
sufficient. For a bidirectional operation, the Residual Count
contains the residual for the write operation.
IE the 'overflow' setting in the iSCSI command response is an indicator
that there _would_ be more data if the command request _would_ have
specified a larger buffer.
But as it didn't, the entire buffer was filled, and the overflow counter
is set.
Which, of course, is then ignored by the linux SCSI stack as the request
got all data, and the residual is set to zero.
Then it's left to the caller to re-send with a larger buffer if
required. But it's nothing the SCSI stack can nor should be attempting
on its own.
As such I think the patch is correct.
Reviewed-by: Hannes Reinecke <hare@xxxxxxx>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@xxxxxxx +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
