Re: [PATCH] tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Bart Van Assche <bvanassche@xxxxxxx>
Subject: Re: [PATCH] tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6)
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Wed, 06 Nov 2019 00:07:30 -0500
Cc: "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, "James E . J . Bottomley" <jejb@xxxxxxxxxxxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>, Hannes Reinecke <hare@xxxxxxxx>, Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
In-reply-to: <20191105215553.185018-1-bvanassche@acm.org> (Bart Van Assche's message of "Tue, 5 Nov 2019 13:55:53 -0800")
Organization: Oracle Corporation
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.92 (gnu/linux)

> According to SBC-2 a TRANSFER LENGTH field of zero means that 256
> logical blocks must be transferred. Make the SCSI tracing code follow
> SBC-2.

Thanks, Bart! Applied to 5.5/scsi-queue.

-- 
Martin K. Petersen	Oracle Linux Engineering

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- [PATCH] tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6)
  - From: Bart Van Assche

Prev by Date: Re: [PATCH 3/3] ufs: Remove .setup_xfer_req()
Next by Date: Re: [PATCH] scsi: scsi-lib.c: increase cmd_size by sizeof(struct scatterlist)
Previous by thread: [PATCH] tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6)
Next by thread: Re: [PATCH] tracing: Fix handling of TRANSFER LENGTH == 0 for READ(6) and WRITE(6)
Index(es):
- Date
- Thread

[Index of Archives] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Samba] [Device Mapper]

Powered by Linux