From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 6/8] nvme: handle invalid SCSI LBAs correctly
Date: Mon, 27 Apr 2015 21:28:32 +0200 [thread overview]
Message-ID: <20150427192832.GA7802@lst.de> (raw)
In-Reply-To: <B58D82457FDA0744A320A2FC5AC253B93BABFA56@fmsmsx104.amr.corp.intel.com>
On Mon, Apr 27, 2015@06:00:13PM +0000, Busch, Keith wrote:
> > Trap LBAs behind the end of the device and return the correct
> > sense code.
>
> Should the driver be responsible to catch these kinds of errors
> on a passthrough IOCTL? Why not let the device deal with it?
Because drives don't seem to report the right error code, and thus
the translation isn't fully spec compliant.
next prev parent reply other threads:[~2015-04-27 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 20:27 NVMe SCSI translation layer updates Christoph Hellwig
2015-04-18 20:27 ` [PATCH 1/8] nvme: remove the unused dma_addr_t arguments to nvme_{get, set}_features Christoph Hellwig
2015-04-18 20:27 ` [PATCH 2/8] nvme: split nvme_trans_send_fw_cmd Christoph Hellwig
2015-04-18 20:27 ` [PATCH 3/8] nvme: fix scsi translation error handling Christoph Hellwig
2015-04-18 20:27 ` [PATCH 4/8] nvme: first round at deobsfucating the scsi translation code Christoph Hellwig
2015-04-18 20:27 ` [PATCH 5/8] nvme: simplify and cleanup the READ/WRITE SCSI CDB parsing code Christoph Hellwig
2015-04-18 20:27 ` [PATCH 6/8] nvme: handle invalid SCSI LBAs correctly Christoph Hellwig
2015-04-27 18:00 ` Busch, Keith
2015-04-27 19:28 ` Christoph Hellwig [this message]
2015-04-27 19:55 ` Keith Busch
2015-05-01 16:02 ` Christoph Hellwig
2015-04-18 20:27 ` [PATCH 7/8] nvme: report the DPOFUA in MODE_SENSE Christoph Hellwig
2015-04-18 20:27 ` [PATCH 8/8] nvme: fail SCSI read/write command with unsupported protection bit Christoph Hellwig
2015-04-21 20:32 ` [PATCH 9/8] nvme: fix kernel memory corruption with short INQUIRY buffers Christoph Hellwig
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=20150427192832.GA7802@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.