From: "Nicholas A. Bellinger" <nab@daterainc.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Calvin Owens <calvinowens@fb.com>,
Christoph Hellwig <hch@infradead.org>,
Sreekanth Reddy <sreekanth.reddy@avagotech.com>,
"MPT-FusionLinux.pdl" <MPT-FusionLinux.pdl@avagotech.com>,
kernel-team <kernel-team@fb.com>,
Nicholas Bellinger <nab@linux-iscsi.org>
Subject: [PATCH-v2 0/2] mpt3sas: Reference counting fixes from for-next mpt2sas
Date: Sun, 30 Aug 2015 07:54:37 +0000 [thread overview]
Message-ID: <1440921279-9973-1-git-send-email-nab@daterainc.com> (raw)
From: Nicholas Bellinger <nab@linux-iscsi.org>
Hi all,
This series is a mpt3sas LLD forward port of Calvin Owens' for-next
reference counting bugfix series for mpt2sas LLD code.
His latest patch series can be found here:
[PATCH v4 0/2] Fixes for memory corruption in mpt2sas
http://marc.info/?l=linux-scsi&m=143951695904115&w=2
The differences between mpt2sas + mpt3sas in this area are very
small, and the changes are required to address a class of long
standing NULL pointer dereference bugs through-out both LLDs.
With Calvin's changes in place for mpt3sas, the original NULL
pointer dereference OOPsen during probe with a failed HDD appear
to be resolved, and so far no new regressions have been reported
with -v1 series code.
The -v1 series code for mpt3sas has been tested on v3.14.47 with
40x SAS3008 HBAs, with three preceeding upstream mpt3sas patches:
4dc06fd mpt3sas: delay scsi_add_host call to work with scsi-mq
35b6236 mpt3sas: combine fw_event_work and its event_data
62c4da4 mpt3sas: correct scsi_{target,device} hostdata allocation
Please review.
--nab
-v2 changes:
- Fix _scsih_block_io_device() v4.3-rc0 brekage
- Fix mpt3sas_transport_port_add() v4.3-rc0 breakage
Nicholas Bellinger (2):
mpt3sas: Refcount sas_device objects and fix unsafe list usage
mpt3sas: Refcount fw_events and fix unsafe list usage
drivers/scsi/mpt3sas/mpt3sas_base.h | 25 +-
drivers/scsi/mpt3sas/mpt3sas_scsih.c | 595 ++++++++++++++++++++++---------
drivers/scsi/mpt3sas/mpt3sas_transport.c | 18 +-
3 files changed, 458 insertions(+), 180 deletions(-)
--
1.9.1
next reply other threads:[~2015-08-30 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 7:54 Nicholas A. Bellinger [this message]
2015-08-30 7:54 ` [PATCH-v2 1/2] mpt3sas: Refcount sas_device objects and fix unsafe list usage Nicholas A. Bellinger
2015-09-08 11:55 ` Sreekanth Reddy
2015-09-09 6:21 ` Nicholas A. Bellinger
2015-09-09 14:29 ` Chaitra Basappa
2015-09-09 22:03 ` Nicholas A. Bellinger
2015-09-11 6:55 ` Nicholas A. Bellinger
2015-09-11 17:50 ` James Bottomley
2015-09-11 20:01 ` Nicholas A. Bellinger
2015-08-30 7:54 ` [PATCH-v2 2/2] mpt3sas: Refcount fw_events " Nicholas A. Bellinger
2015-09-04 18:47 ` [PATCH-v2 0/2] mpt3sas: Reference counting fixes from for-next mpt2sas Nicholas A. Bellinger
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=1440921279-9973-1-git-send-email-nab@daterainc.com \
--to=nab@daterainc.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=MPT-FusionLinux.pdl@avagotech.com \
--cc=calvinowens@fb.com \
--cc=hch@infradead.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=sreekanth.reddy@avagotech.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
all inboxes | Powered by JetHome®