linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] SG_SCSI_RESET ioctl should only perform requested operation
@ 2013-02-04 20:17 Jeremy Linton
  2013-02-04 22:28 ` Douglas Gilbert
  0 siblings, 1 reply; 2+ messages in thread
From: Jeremy Linton @ 2013-02-04 20:17 UTC (permalink / raw)
  To: Linux Scsi

>From all the documentation I've found, it is not clear that users of the
SG_SCSI_RESET ioctl may have their requests progress up the hierarchy of reset
operations.

Basically, requests for a SCSI_TRY_RESET_DEVICE may eventually result in a
TARGET, BUS, or HOST reset. The sg_reset utility hints at the error handling,
but actually leads the user to believe that they should reissue the sg_reset
command themselves to enact more aggressive reset functions. It also says:
"Note that a host reset and a bus reset may cause collateral damage."

In the interest of error isolation, I have attached a patch which changes the
behavior. The existing behavior is obviously intentional, but I don't believe
its the best choice.

There are other alternatives to this patch. For one, to avoid the possibility of
breaking an existing application, maybe SG_SCSI_RESET needs some new values like
"SG_SCSI_RESET_DEVICE_ONLY". While leaving the existing operations alone.



Just in case...
Signed-off-by: Jeremy Linton <jlinton@tributary.com>
---
	
diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
index c1b05a8..6f05bc2 100644
--- a/drivers/scsi/scsi_error.c
+++ b/drivers/scsi/scsi_error.c
@@ -1999,19 +1999,13 @@ scsi_reset_provider(struct scsi_device *dev, int flag)
        switch (flag) {
        case SCSI_TRY_RESET_DEVICE:
                rtn = scsi_try_bus_device_reset(scmd);
-               if (rtn == SUCCESS)
-                       break;
-               /* FALLTHROUGH */
+               break;
        case SCSI_TRY_RESET_TARGET:
                rtn = scsi_try_target_reset(scmd);
-               if (rtn == SUCCESS)
-                       break;
-               /* FALLTHROUGH */
+               break;
        case SCSI_TRY_RESET_BUS:
                rtn = scsi_try_bus_reset(scmd);
-               if (rtn == SUCCESS)
-                       break;
-               /* FALLTHROUGH */
+               break;
        case SCSI_TRY_RESET_HOST:
                rtn = scsi_try_host_reset(scmd);
                break;

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] SG_SCSI_RESET ioctl should only perform requested operation
  2013-02-04 20:17 [PATCH] SG_SCSI_RESET ioctl should only perform requested operation Jeremy Linton
@ 2013-02-04 22:28 ` Douglas Gilbert
  0 siblings, 0 replies; 2+ messages in thread
From: Douglas Gilbert @ 2013-02-04 22:28 UTC (permalink / raw)
  To: Jeremy Linton; +Cc: Linux Scsi

On 13-02-04 03:17 PM, Jeremy Linton wrote:
>>From all the documentation I've found, it is not clear that users of the
> SG_SCSI_RESET ioctl may have their requests progress up the hierarchy of reset
> operations.
>
> Basically, requests for a SCSI_TRY_RESET_DEVICE may eventually result in a
> TARGET, BUS, or HOST reset. The sg_reset utility hints at the error handling,
> but actually leads the user to believe that they should reissue the sg_reset
> command themselves to enact more aggressive reset functions. It also says:
> "Note that a host reset and a bus reset may cause collateral damage."
>
> In the interest of error isolation, I have attached a patch which changes the
> behavior. The existing behavior is obviously intentional, but I don't believe
> its the best choice.
>
> There are other alternatives to this patch. For one, to avoid the possibility of
> breaking an existing application, maybe SG_SCSI_RESET needs some new values like
> "SG_SCSI_RESET_DEVICE_ONLY". While leaving the existing operations alone.
>
>
>
> Just in case...
> Signed-off-by: Jeremy Linton <jlinton@tributary.com>
> ---
> 	
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index c1b05a8..6f05bc2 100644
> --- a/drivers/scsi/scsi_error.c
> +++ b/drivers/scsi/scsi_error.c
> @@ -1999,19 +1999,13 @@ scsi_reset_provider(struct scsi_device *dev, int flag)
>          switch (flag) {
>          case SCSI_TRY_RESET_DEVICE:
>                  rtn = scsi_try_bus_device_reset(scmd);
> -               if (rtn == SUCCESS)
> -                       break;
> -               /* FALLTHROUGH */
> +               break;
>          case SCSI_TRY_RESET_TARGET:
>                  rtn = scsi_try_target_reset(scmd);
> -               if (rtn == SUCCESS)
> -                       break;
> -               /* FALLTHROUGH */
> +               break;
>          case SCSI_TRY_RESET_BUS:
>                  rtn = scsi_try_bus_reset(scmd);
> -               if (rtn == SUCCESS)
> -                       break;
> -               /* FALLTHROUGH */
> +               break;
>          case SCSI_TRY_RESET_HOST:
>                  rtn = scsi_try_host_reset(scmd);
>                  break;
> --

Jeremy,
That is way too sensible to be approved as it will most likely
break existing code that assumes the escalation property.

Perhaps some new constants could be introduced (e.g.
SCSI_TRY_RESET_TARGET_ONLY) that could be passed to
the SG_SCSI_RESET ioctl. And perhaps that new set of
constants could more accurately reflect how such things
are done in modern SCSI.

Doug Gilbert



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-02-04 22:28 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-04 20:17 [PATCH] SG_SCSI_RESET ioctl should only perform requested operation Jeremy Linton
2013-02-04 22:28 ` Douglas Gilbert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).