public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Linton <jlinton@tributary.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "dgilbert@interlog.com" <dgilbert@interlog.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [GIT PULL] Final round of SCSI updates for the 3.8+ merge window
Date: Fri, 1 Mar 2013 09:27:00 -0600	[thread overview]
Message-ID: <5130C8C4.3020501@tributary.com> (raw)
In-Reply-To: <1362150419.2384.29.camel@dabdike.int.hansenpartnership.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 3/1/2013 9:06 AM, James Bottomley wrote:

>> 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.
>> 
> So the patch does seem to have dangerous side effects.

	Those are due to "bugs" in the LLD's that actually are there regardless of
that patch. For example the lpfc patch I posted a couple days ago, fixes the
LPFC driver so that it actually checks the return status from the task
management IOCB's being sent to the firmware. As it stands the reset paths in
the lpfc driver always return SUCCESS independently of the status of any
aborts, resets, being sent as part of the reset handlers. This is completely
non obvious at first glance at the code.


	This means that the error handling behavior of lpfc is significantly
different (and not necessarily better) than the zfcp and qlogic drivers I also
tested.

	I didn't find any cases where this patch makes the problem worse, in fact in
general the behavior is significantly better.


	

	


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRMMjEAAoJEL5i86xrzcy7qrsH/3l0hz22pp/QJsZ2XJghpH/s
L8c1m5h9mTvSMFUtFIQoLkclHgJcVkTs7aeHLeEFxzZ5vEPPbuieLkr78s5Z3iVa
99LuuIMKSPZWpgohSVL0xsaaDftc4xVQ09MuuLWNeTxNZvKGRUalyVDLoPthSEwz
MXKNng6K1IqBe+u1mS+QhfAqNS5EVOI3gx34XIa0rm81jEKNeVpIF9qU0pCuJnNs
4QeYH+66hK+ILVyRyn+qsdjg8vT5xccaGw1DUbEzxz2QATKP0HOPG+dnlyzPkb4r
12UvBtHqT6+QRFeBe+sdgWRCwszaOOTjH18kMMUZaJJB3EaCV3dJsVESMO4K0GI=
=IueP
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-03-01 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01  9:19 [GIT PULL] Final round of SCSI updates for the 3.8+ merge window James Bottomley
2013-03-01 13:27 ` Douglas Gilbert
2013-03-01 13:51   ` Paolo Bonzini
2013-03-01 15:06   ` James Bottomley
2013-03-01 15:27     ` Jeremy Linton [this message]
2013-03-01 17:03       ` Douglas Gilbert
2013-03-01 16:14 ` Bart Van Assche
2013-03-07 15:33 ` Martin Peschke

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=5130C8C4.3020501@tributary.com \
    --to=jlinton@tributary.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dgilbert@interlog.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    /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