From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>,
Steven Williamson <steven.williamson@dialogue.net>,
james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
mikem@beardog.cce.hp.com, stephenmcameron@gmail.com,
thenzl@redhat.com, scott.teel@hp.com, akpm@linux-foundation.org
Subject: [3.0.y, 3.2.y, 3.3.y] Re: [PATCH 05/10] hpsa: Fix problem with MSA2xxx devices
Date: Sun, 20 May 2012 04:47:35 -0500 [thread overview]
Message-ID: <20120520094735.GA14683@burratino> (raw)
In-Reply-To: <20120119200104.17835.29536.stgit@beardog.cce.hp.com>
Hi Greg and Ben,
Please consider
9bc3711cbb67 [SCSI] hpsa: Fix problem with MSA2xxx devices
for application to next week's 3.0.y, 3.2.y, and 3.3.y trees.
As Steven Williamson noticed[1], without this patch:
> The hpsa driver fails to correctly assign devices when there are
> multiple paths on at least the Smart Array 712m with the latest
> firmware.
>
> The end result is only one device node is created in /dev and multipath
> tools then only detect one path.
He tested this patch + fda38518f236 "[SCSI] hpsa: add P2000 to list of
shared SAS devices" (which is already in v3.0) on top of a
2.6.32.y-based kernel and found:
> Applying the patch here:
> http://www.spinics.net/lists/linux-scsi/msg56690.html
> to the current stable version of the squeeze kernel fixes the issue.
>
> This was tested on a Smart Array 712m, connected via 2 SAS switches to a
> HP P2000 G3 SAS Array.
Stephen, are any other patches from the series at [2] or elsewhere
candidates for inclusion in stable trees?
Thanks and hope that helps,
Jonathan
[1] http://bugs.debian.org/661057
[2] http://thread.gmane.org/gmane.linux.kernel/1241509
next prev parent reply other threads:[~2012-05-20 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 20:00 [PATCH 01/10] hpsa: fix per device memory leak on driver unload Stephen M. Cameron
2012-01-19 20:00 ` [PATCH 02/10] hpsa: removed unneeded structure member max_sg_entries and fix badly named constant MAXSGENTRIES Stephen M. Cameron
2012-01-19 20:00 ` [PATCH 03/10] hpsa: combine hpsa_scsi_detect and hpsa_register_scsi Stephen M. Cameron
2012-01-19 20:00 ` [PATCH 04/10] hpsa: factor out driver name Stephen M. Cameron
2012-01-19 20:01 ` [PATCH 05/10] hpsa: Fix problem with MSA2xxx devices Stephen M. Cameron
2012-05-20 9:47 ` Jonathan Nieder [this message]
2012-05-22 2:17 ` [3.0.y, 3.2.y, 3.3.y] " Ben Hutchings
2012-05-24 19:11 ` Greg KH
2012-05-24 22:02 ` Jonathan Nieder
2012-01-19 20:01 ` [PATCH 06/10] hpsa: make target and lun match what SCSI REPORT LUNs returns Stephen M. Cameron
2012-01-19 20:01 ` [PATCH 07/10] hpsa: refactor hpsa_figure_bus_target_lun Stephen M. Cameron
2012-01-19 20:01 ` [PATCH 08/10] hpsa: eliminate 8 external target limitation Stephen M. Cameron
2012-01-19 20:01 ` [PATCH 09/10] hpsa: improve naming on external target device functions Stephen M. Cameron
2012-01-19 20:01 ` [PATCH 10/10] hpsa: update device attributes when they change Stephen M. Cameron
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=20120520094735.GA14683@burratino \
--to=jrnieder@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=scott.teel@hp.com \
--cc=stable@vger.kernel.org \
--cc=stephenmcameron@gmail.com \
--cc=steven.williamson@dialogue.net \
--cc=thenzl@redhat.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 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).