From: James Bottomley <James.Bottomley@SteelEye.com>
To: Michael Reed <mdr@sgi.com>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
James.Smart@Emulex.Com, Jeremy Higdon <jeremy@sgi.com>
Subject: Re: [PATCH] OOPS due to clearing eh_action prior to aborting eh command
Date: Wed, 07 Dec 2005 17:06:44 -0500 [thread overview]
Message-ID: <1133993204.3303.46.camel@mulgrave> (raw)
In-Reply-To: <43975A8C.2030208@sgi.com>
On Wed, 2005-12-07 at 15:56 -0600, Michael Reed wrote:
> During my testing of fc transport attributes for the mpt fusion
> driver, I came upon this OOPS. (Actually, I've come upon it
> too many times. :( )
>
> Attached is a patch which addresses the issue. Please give it a look.
Isn't a better patch simply to copy the eh_action and check it for null
before completing it? That will close the done after timeout race.
James
next prev parent reply other threads:[~2005-12-07 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 21:56 [PATCH] OOPS due to clearing eh_action prior to aborting eh command Michael Reed
2005-12-07 22:06 ` James Bottomley [this message]
2005-12-07 22:16 ` Michael Reed
2005-12-07 23:34 ` James Bottomley
2005-12-08 2:31 ` Michael Reed
2005-12-08 3:46 ` Michael Reed
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=1133993204.3303.46.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.Com \
--cc=hch@lst.de \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.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 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.