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: Wed, 23 Mar 2011 19:02:59 -0400 [thread overview]
Message-ID: <20110323230259.GA3758@redhat.com> (raw)
In-Reply-To: <1300917791.15899.39.camel@mulgrave.site>
On Wed, Mar 23 2011 at 6:03pm -0400,
James Bottomley <James.Bottomley@suse.de> wrote:
> On Wed, 2011-03-23 at 17:58 -0400, Mike Snitzer wrote:
> > On Mon, Mar 21 2011 at 7:16pm -0400,
> > Mike Snitzer <snitzer@redhat.com> wrote:
> >
> > > > It's a bug fix: of course it can.
> > >
> > > Right, so given scsi_dh_activate()'s {get,put}_device() that wraps the
> > > call to scsi_dh->activate (aka clariion_activate) I'm not seeing how
> > > accessing sdev->sdev_gendev (via sdev_printk) could result in a panic.
> > > So I'll need to dig deeper (hopefully with Eddie's assistance)...
> >
> > Hi James,
> >
> > I checked with Eddie and the sdev_printk() panic he saw no longer occurs
> > when commit db422318 is in place. But he also tested with the patch I
> > provided below.
> >
> > I still feel this fix is needed and would like to get your feedback on
> > this (relative to 2.6.39):
>
> So what about the fix you propose in
>
> Message-id: <20110321231657.GA12902@redhat.com>
>
> ? That looks to be the correct one.
Yes, that is the correct fix (that is the same patch I quoted in my mail
preceeding this one).
We'd need it in 2.6.38.y too.
Thanks,
Mike
prev parent reply other threads:[~2011-03-23 23:03 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
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 [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=20110323230259.GA3758@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).