From: Akinobu Mita <akinobu.mita@gmail.com>
To: linux-scsi@vger.kernel.org, "James E.J. Bottomley" <JBottomley@odin.com>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
Don Brace <don.brace@pmcs.com>,
iss_storagedev@hp.com, storagedev@pmcs.com,
Adam Radford <linuxraid@lsi.com>,
Kashyap Desai <kashyap.desai@avagotech.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
megaraidlinux.pdl@avagotech.com
Subject: [PATCH 0/7] scsi: Fix transfer length 0 for 6-byte r/w commands
Date: Sat, 16 May 2015 16:17:46 +0900 [thread overview]
Message-ID: <1431760673-7180-1-git-send-email-akinobu.mita@gmail.com> (raw)
For 6-byte r/w commands, transfer length 0 means 256 blocks of data,
not 0 block.
But some drivers consider transfer length 0 as 0 block.
Fortunately, the scsi disk driver sets up 10-byte r/w commands for
256 blocks of data instead of 6-byte r/w commands. So this could be
an issue when SCSI commands are issued by SG_IO ioctl.
Akinobu Mita (7):
hpsa: fix transfer length 0 for 6-byte r/w commands
3w-xxxx: fix transfer length 0 for 6-byte r/w commands
3w-9xxx: fix transfer length 0 for 6-byte r/w commands
scsi: trace: fix transfer length 0 for 6-byte r/w commands
staging: rts5208: fix transfer length 0 for 6-byte r/w commands
megaraid_mbox: fix transfer length 0 for 6-byte r/w commands
megaraid: fix transfer length 0 for 6-byte r/w commands
drivers/scsi/3w-9xxx.c | 5 ++++-
drivers/scsi/3w-xxxx.c | 2 ++
drivers/scsi/hpsa.c | 2 ++
drivers/scsi/megaraid.c | 2 ++
drivers/scsi/megaraid/megaraid_mbox.c | 2 ++
drivers/scsi/scsi_trace.c | 2 ++
drivers/staging/rts5208/rtsx_scsi.c | 8 ++++++--
7 files changed, 20 insertions(+), 3 deletions(-)
Cc: Don Brace <don.brace@pmcs.com>
Cc: iss_storagedev@hp.com
Cc: storagedev@pmcs.com
Cc: Adam Radford <linuxraid@lsi.com>
Cc: Kashyap Desai <kashyap.desai@avagotech.com>
Cc: Sumit Saxena <sumit.saxena@avagotech.com>
Cc: Uday Lingala <uday.lingala@avagotech.com>
Cc: megaraidlinux.pdl@avagotech.com
Cc: "James E.J. Bottomley" <JBottomley@odin.com>
Cc: linux-scsi@vger.kernel.org
--
1.9.1
next reply other threads:[~2015-05-16 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 7:17 Akinobu Mita [this message]
2015-05-16 7:17 ` [PATCH 1/7] hpsa: fix transfer length 0 for 6-byte r/w commands Akinobu Mita
2015-05-16 7:17 ` [PATCH 2/7] 3w-xxxx: " Akinobu Mita
2015-05-16 7:17 ` [PATCH 3/7] 3w-9xxx: " Akinobu Mita
2015-05-16 7:17 ` [PATCH 4/7] scsi: trace: " Akinobu Mita
2015-05-16 7:17 ` [PATCH 5/7] staging: rts5208: " Akinobu Mita
2015-05-16 7:17 ` [PATCH 6/7] megaraid_mbox: " Akinobu Mita
2015-05-16 7:17 ` [PATCH 7/7] megaraid: " Akinobu Mita
2015-05-16 16:46 ` [PATCH 0/7] scsi: Fix " James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431760673-7180-1-git-send-email-akinobu.mita@gmail.com \
--to=akinobu.mita@gmail.com \
--cc=JBottomley@odin.com \
--cc=don.brace@pmcs.com \
--cc=iss_storagedev@hp.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxraid@lsi.com \
--cc=megaraidlinux.pdl@avagotech.com \
--cc=storagedev@pmcs.com \
--cc=sumit.saxena@avagotech.com \
--cc=uday.lingala@avagotech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox