From: Maximilian Wilhelm <max@rfc2324.org>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
akpm@linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>,
mm-commits@vger.kernel.org, Eric.Moore@lsi.com,
fujita.tomonori@lab.ntt.co.jp, ole@ans.pl,
sathya.prakash@lsi.com, max@rfc2324.org
Subject: Re: + mpt-fusion-dont-oops-if-numphys==0.patch added to -mm tree
Date: Wed, 20 Feb 2008 04:17:31 +0100 [thread overview]
Message-ID: <20080220031731.GA31633@outback.rfc2324.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802200400001.6490@bizon.gios.gov.pl>
Am Wednesday, den 20 February hub Krzysztof Oledzki folgendes in die Tasten:
Hi Krzysztof, *
Thanks for CC'ing me.
> >On Tue, 2008-02-19 at 15:34 -0800, akpm@linux-foundation.org wrote:
> >>Subject: mpt fusion: don't oops if NumPhys==0
> >>From: Krzysztof Oledzki <olel@ans.pl>
> >>
> >>Don't oops if NumPhys==0, instead return -ENODEV.
> >>This patch fixes http://bugzilla.kernel.org/show_bug.cgi?id=9909
> >>
> >>Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>
> >>Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> >>Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
> >>Cc: Eric Moore <Eric.Moore@lsi.com>
> >>Cc: Sathya Prakash <sathya.prakash@lsi.com>
> >>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> >>---
> >>
> >> drivers/message/fusion/mptsas.c | 5 +++++
> >> 1 file changed, 5 insertions(+)
> >>
> >>diff -puN
> >>drivers/message/fusion/mptsas.c~mpt-fusion-dont-oops-if-numphys==0
> >>drivers/message/fusion/mptsas.c
> >>--- a/drivers/message/fusion/mptsas.c~mpt-fusion-dont-oops-if-numphys==0
> >>+++ a/drivers/message/fusion/mptsas.c
> >>@@ -1701,6 +1701,11 @@ mptsas_sas_expander_pg0(MPT_ADAPTER *ioc
> >> if (error)
> >> goto out_free_consistent;
> >>
> >>+ if (!buffer->NumPhys) {
> >>+ error = -ENODEV;
> >>+ goto out_free_consistent;
> >>+ }
> >>+
> >> /* save config data */
> >> port_info->num_phys = buffer->NumPhys;
> >> port_info->phy_info = kcalloc(port_info->num_phys,
> >>_
> >
> >This is a bit odd ... It looks like a work around for a fusion firmware
> >problem.
> Workaround or not, the driver should not oops by allocating 0 size memory
> block and dereferencing it. It used to work in <2.6.23 but not now.
ACK.
Nevertheless my server is working absolutely well with this
fix/workaround. No problems at all.
> >What's the topology this thing is connected to?
> It is a Dell-1950III server with two 400GB SAS disks (RAID1) installed in
> a dwo disk SAS backplane.
Here it's a Dell 1950 with two 73G SAS disks (RAID1) but having four
SAS disk slots.
If you need further information about the hardware, just let me know.
Ciao
Max
--
Follow the white penguin.
next prev parent reply other threads:[~2008-02-20 3:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802192335.m1JNZ7MV005426@imap1.linux-foundation.org>
2008-02-20 2:39 ` + mpt-fusion-dont-oops-if-numphys==0.patch added to -mm tree James Bottomley
2008-02-20 3:06 ` Krzysztof Oledzki
2008-02-20 3:17 ` Maximilian Wilhelm [this message]
2008-02-20 3:28 ` James Bottomley
2008-02-20 18:14 ` Maximilian Wilhelm
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=20080220031731.GA31633@outback.rfc2324.org \
--to=max@rfc2324.org \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ole@ans.pl \
--cc=olel@ans.pl \
--cc=sathya.prakash@lsi.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