From: Jeremy Linton <jlinton@tributary.com>
To: "dgilbert@interlog.com" <dgilbert@interlog.com>
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH v2] SG_SCSI_RESET ioctl: add no_escalate values
Date: Fri, 22 Feb 2013 15:30:11 -0600 [thread overview]
Message-ID: <5127E363.9060100@tributary.com> (raw)
In-Reply-To: <511FD7DE.3040606@interlog.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tested-by: Jeremy Linton jlinton@tributary.com
I tested this patch in an environment where the lun and target reset is
"failing" because the target device is misbehaving.
This patch appears to work as advertised.
That said, I changed my testing methodology for this patch (vs the one I
originally posted). The results were "interesting", there are some really
strange things that happen in some of the LLD error paths. Its obvious that
error injection is not part of testing many of them, and what at first glance
should be a fairly straightforward error can create quite a mess. So anyone
sending any kind of reset (especially without the ESCALATE flag which tends to
isolate the error handling) to the LLD's should be aware that behavior between
them can vary significantly.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRJ+NjAAoJEL5i86xrzcy7GI0H/2XKCZvhLmE8WeQtMXlHhVyA
G3Y34fKeEx9ek56Sr6AcipvV9mUBR9uYvydxZfdGjBT83I2bYGRHEfVEx22WKFXr
JShVv43eIl5y/inUr8THNTBfggFcYaBIx21ieLwvR/+cBGWbpiIwi16ktaENX2O7
nHgHVSvFOam9Qy8ewQ2YcULsGFkHQd1SN2LXKSh5bp42eZ998Od4t+agADlNipNz
OShNyJO9fHr4XC/pNMdujjDd+eaOPv5/furYAgkU/aQutxjIs5a0OtDiNi0hzmQ+
ZVfoQWk4Bh4LJdQ2ZiqiKBi54z8YxJu5n2WmbKTzwWcabumOWqebNG8JaYDDYjI=
=2mMo
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-02-22 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 19:02 [PATCH v2] SG_SCSI_RESET ioctl: add no_escalate values Douglas Gilbert
2013-02-22 21:30 ` Jeremy Linton [this message]
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=5127E363.9060100@tributary.com \
--to=jlinton@tributary.com \
--cc=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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.