linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, Eddie Williams <eddie.williams@steeleye.com>
Subject: Re: [PATCH for-2.6.39] [SCSI] scsi_dh_emc: fix panic when handling multiple path failures
Date: Mon, 21 Mar 2011 16:38:29 -0400	[thread overview]
Message-ID: <20110321203829.GB12157@redhat.com> (raw)
In-Reply-To: <1300737774.10634.37.camel@mulgrave.site>

On Mon, Mar 21 2011 at  4:02pm -0400,
James Bottomley <James.Bottomley@suse.de> wrote:

> On Mon, 2011-03-21 at 15:57 -0400, Mike Snitzer wrote:
> > From: Eddie Williams <eddie.williams@steeleye.com>
> > 
> > Do not sdev_printk() a scsi_device that was, or is being, deleted.
> > 
> > If multiple failures occur (e.g. FC switch with multiple paths fails),
> > and both the active path and next path is failed in the process, the
> > scsi_device associated with the next path can be accessed after it was
> > deleted.
> 
> This treats the symptom, not the cause, doesn't it?  Why do we have a
> reference to an ungot instance of an sdev here ... and should it have
> had a reference taken on it?

Stands to reason, and to be fair Eddie thought that might be the case
too -- I should have shared as much.  I'll take a closer look (quite
busy this week but...).

Finding the root cause in the near-term would be ideal.  Short of that
this "fix" isn't unreasonable.  Only problem with taking it would be if
someone like me didn't know to actively chase the real problem with this
"fix" reverted.  Whereby papering over the real issue.

Anyway, it's now on my plate to sort out.  No idea if I'll do so by the
close of the merge window.  But maybe a real fix to this can go in after
the window closes?

I guess time will tell, thanks.
Mike

  reply	other threads:[~2011-03-21 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 19:57 [PATCH for-2.6.39] [SCSI] scsi_dh_emc: fix panic when handling multiple path failures Mike Snitzer
2011-03-21 20:02 ` James Bottomley
2011-03-21 20:38   ` Mike Snitzer [this message]
2011-03-21 20:44     ` James Bottomley
2011-03-21 23:16       ` Mike Snitzer
     [not found]         ` <AANLkTimknz6=6CeURQD_ZB+9DD9W20-rfktjp75nsZrW@mail.gmail.com>
2011-03-22  2:36           ` Eddie Williams
2011-03-23 21:58         ` Mike Snitzer
2011-03-23 22:03           ` James Bottomley
2011-03-23 23:02             ` Mike Snitzer

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=20110321203829.GB12157@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@suse.de \
    --cc=eddie.williams@steeleye.com \
    --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;
as well as URLs for NNTP newsgroup(s).