lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 10 Dec 2013 10:53:59 +0530
From:	Vishal Annapurve <vannapurve@...dia.com>
To:	Greg KH <greg@...ah.com>
CC:	Alan Stern <stern@...land.harvard.edu>,
	Ming Lei <tom.leiming@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb <linux-usb@...r.kernel.org>
Subject: Re: [PATCH] usb-storage: scsiglue: Changing the command result

Hi Greg,

Does this look fine? I will send over other patches
once you confirm.

Patch set 1:
---------
[PATCH 1/3] usb: storage: Proper cmd result assignment

This change replaces DID_ABORT with DID_TIMEOUT as a command result
whenever US_FLIDX_TIMED_OUT bit is set.

This change is made to bring USB storage inline with a recent change:

commit    18a4d0a22ed6c54b67af7718c305cd010f09ddf8

[SCSI] Handle disk devices which can not process medium access commands
We have experienced several devices which fail in a fashion we do not
currently handle gracefully in SCSI. After a failure these devices will
respond to the SCSI primary command set (INQUIRY, TEST UNIT READY, etc.)
but any command accessing the storage medium will time out.

As the USB storage was setting command result as aborted rather than
timed out, SCSI layer was not recognizing the above mentioned failure
pattern.

Signed-off-by: Vishal Annapurve <vannapurve@...dia.com>
---
  drivers/usb/storage/cypress_atacb.c |  1 +
  drivers/usb/storage/isd200.c        |  2 +-
  drivers/usb/storage/transport.c     |  8 ++++----
  drivers/usb/storage/usb.c           | 10 ++++++----
  4 files changed, 12 insertions(+), 9 deletions(-)
---
diff --git a/drivers/usb/storage/cypress_atacb.c 
b/drivers/usb/storage/cypress_atacb.c
index 8514a2d..3477ca19 100644
--- a/drivers/usb/storage/cypress_atacb.c
+++ b/drivers/usb/storage/cypress_atacb.c
@@ -168,6 +168,7 @@ static void cypress_atacb_passthrough(struct 
scsi_cmnd *srb, struct us_data *us)
       */
      if ((srb->result != (DID_ERROR << 16) &&
                  srb->result != (DID_ABORT << 16)) &&
+                srb->result != (DID_TIME_OUT << 16) &&
              save_cmnd[2] & 0x20) {
          struct scsi_eh_save ses;
          unsigned char regs[8];
diff --git a/drivers/usb/storage/isd200.c b/drivers/usb/storage/isd200.c
index 599d8bf..ffd5d58 100644
--- a/drivers/usb/storage/isd200.c
+++ b/drivers/usb/storage/isd200.c
@@ -703,7 +703,7 @@ static void isd200_invoke_transport( struct us_data *us,
      /* abort processing: the bulk-only transport requires a reset
       * following an abort */
      Handle_Abort:
-    srb->result = DID_ABORT << 16;
+    srb->result = DID_TIME_OUT << 16;

      /* permit the reset transfer to take place */
      clear_bit(US_FLIDX_ABORTING, &us->dflags);
diff --git a/drivers/usb/storage/transport.c 
b/drivers/usb/storage/transport.c
index 22c7d43..6a90161 100644
--- a/drivers/usb/storage/transport.c
+++ b/drivers/usb/storage/transport.c
@@ -607,8 +607,8 @@ void usb_stor_invoke_transport(struct scsi_cmnd 
*srb, struct us_data *us)
       * short-circuit all other processing
       */
      if (test_bit(US_FLIDX_TIMED_OUT, &us->dflags)) {
-        usb_stor_dbg(us, "-- command was aborted\n");
-        srb->result = DID_ABORT << 16;
+        usb_stor_dbg("-- command was aborted because of timeout\n");
+        srb->result = DID_TIME_OUT << 16;
          goto Handle_Errors;
      }

@@ -717,8 +717,8 @@ Retry_Sense:
          scsi_eh_restore_cmnd(srb, &ses);

          if (test_bit(US_FLIDX_TIMED_OUT, &us->dflags)) {
-            usb_stor_dbg(us, "-- auto-sense aborted\n");
-            srb->result = DID_ABORT << 16;
+            usb_stor_dbg("-- auto-sense aborted due to timeout\n");
+            srb->result = DID_TIME_OUT << 16;

              /* If SANE_SENSE caused this problem, disable it */
              if (sense_size != US_SENSE_SIZE) {
diff --git a/drivers/usb/storage/usb.c b/drivers/usb/storage/usb.c
index 5c4fe07..04a68eb 100644
--- a/drivers/usb/storage/usb.c
+++ b/drivers/usb/storage/usb.c
@@ -325,7 +325,7 @@ static int usb_stor_control_thread(void * __us)

          /* has the command timed out *already* ? */
          if (test_bit(US_FLIDX_TIMED_OUT, &us->dflags)) {
-            us->srb->result = DID_ABORT << 16;
+            us->srb->result = DID_TIME_OUT << 16;
              goto SkipForAbort;
          }

@@ -379,7 +379,8 @@ static int usb_stor_control_thread(void * __us)
          scsi_lock(host);

          /* indicate that the command is done */
-        if (us->srb->result != DID_ABORT << 16) {
+        if ((us->srb->result != DID_ABORT << 16) &&
+            (us->srb->result != DID_TIME_OUT << 16)) {
              usb_stor_dbg(us, "scsi cmd done, result=0x%x\n",
                       us->srb->result);
              us->srb->scsi_done(us->srb);
@@ -390,8 +391,9 @@ SkipForAbort:

          /* If an abort request was received we need to signal that
           * the abort has finished.  The proper test for this is
-         * the TIMED_OUT flag, not srb->result == DID_ABORT, because
-         * the timeout might have occurred after the command had
+         * the TIMED_OUT flag, not srb->result == DID_ABORT or
+         * srb->result == DID_TIMEOUT , because the timeout might
+         * have occurred after the command had
           * already completed with a different result code. */
          if (test_bit(US_FLIDX_TIMED_OUT, &us->dflags)) {
              complete(&(us->notify));
---

Regards,
Vishal

On Monday 09 December 2013 04:53 PM, Greg KH wrote:
> On Mon, Dec 09, 2013 at 03:14:07PM +0530, Vishal Annapurve wrote:
>> Hi Greg,
>>
>> Attached are the patches.
> As Oliver said, I can't take these, please read
> Documentation/SubmittingPatches for how to do this properly.
>
> thanks,
>
> greg k-h

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ