On Tue, Dec 14, 2021 at 09:16:51AM -0500, George Kennedy wrote:

Avoid data corruption by rejecting pass-through commands where T_LENGTH is zero (No data is transferred) and the dma direction is not DMA_NONE.

Cc: stable@vger.kernel.org Reported-by: syzkallersyzkaller@googlegroups.com Signed-off-by: George Kennedygeorge.kennedy@oracle.com

---

drivers/ata/libata-scsi.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c index 1b84d55..313e947 100644 --- a/drivers/ata/libata-scsi.c +++ b/drivers/ata/libata-scsi.c @@ -2859,8 +2859,19 @@ static unsigned int ata_scsi_pass_thru(struct ata_queued_cmd *qc) goto invalid_fld; }

• if (ata_is_ncq(tf->protocol) && (cdb[2 + cdb_offset] & 0x3) == 0)

• tf->protocol = ATA_PROT_NCQ_NODATA;
  

• if ((cdb[2 + cdb_offset] & 0x3) == 0) {

• /*
  

•  * When T_LENGTH is zero (No data is transferred), dir should
  

•  * be DMA_NONE.
  

•  */
  

• if (scmd->sc_data_direction != DMA_NONE) {
  

• 	fp = 2 + cdb_offset;
  

• 	goto invalid_fld;
  

• }
  

• if (ata_is_ncq(tf->protocol))
  

• 	tf->protocol = ATA_PROT_NCQ_NODATA;
  

• }

/* enable LBA */ tf->flags |= ATA_TFLAG_LBA; -- 1.8.3.1

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.

You are receiving this message because of the following common error(s) as indicated below:

- This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.

thanks,

greg k-h's patch email bot