public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI testing/USB devices are amazing
Date: Thu, 09 May 2013 22:43:27 -0400	[thread overview]
Message-ID: <yq1k3n7eer4.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAN05THR+P7nzzTe6FCmG+F8_frkL=z-PS1GvoBVn57EyDMo-dw@mail.gmail.com> (ronnie sahlberg's message of "Sun, 28 Apr 2013 09:19:36 -0700")

>>>>> "Ronnie" == ronnie sahlberg <ronniesahlberg@gmail.com> writes:

Ronnie> * please have a look at the tests and the test results I linked
Ronnie>   to above. I currently have quite a few tests but am happy to
Ronnie>   add more.

Aside from issuing commands with various bits set, I'd like to see some
more sanity checking. Mainly to see whether it responds correctly to the
features is claims to support.

I.e. do the values reported in the Block Limits VPD look sane given what
we know about the device in general (SCSI level, capacity, PI supported,
discard supported, etc.)?

Right now you always expect RDPROTECT/WRPROTECT > 0 to fail, but they
should succeed if the device is formatted with PI.

FWIW, my slightly outdated document is here:

	https://oss.oracle.com/~mkp/docs/linux-advanced-storage.pdf

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2013-05-10  2:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-28 16:19 SCSI testing/USB devices are amazing ronnie sahlberg
2013-05-10  2:43 ` Martin K. Petersen [this message]
2013-05-14  2:36   ` ronnie sahlberg
2013-05-14 22:43     ` Martin K. Petersen
2013-05-17 23:53       ` ronnie sahlberg
2013-05-19 17:39         ` Douglas Gilbert
2013-05-22 14:07 ` Bart Van Assche
2013-05-22 17:05   ` ronnie sahlberg

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=yq1k3n7eer4.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=ronniesahlberg@gmail.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