On 4/15/2015 7:10 PM, Martin K. Petersen wrote:
"Sagi" == Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx> writes:By the commit 436f4a0a ("loopback: Add fabric_prot_type attribute support"), When WRITE_SAME command with WRPROTECT=0 is executed, sbc_dif_generate() is called but cmd->t_prot_sg is NULL as block layer didn't allocate it for WRITE_SAME.Sagi> Actually this is a bug. Why didn't the initiator allocate Sagi> integrity meta-data for WRITE_SAME? Looking at the code it looks Sagi> like it should. We don't issue WRITE SAME with PI so there is no prot SGL.
Is there a specific reason why we don't? -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
