From: Boaz Harrosh <bharrosh@panasas.com>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
"pterjan@gmail.com" <pterjan@gmail.com>,
"matthew@wil.cx" <matthew@wil.cx>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Patro, Sumant" <Sumant.Patro@lsi.com>,
"bugme-daemon@bugzilla.kernel.org"
<bugme-daemon@bugzilla.kernel.org>,
"Austria, Winston" <Winston.Austria@lsi.com>
Subject: Re: [Bugme-new] [Bug 11792] New: Oops when reading /proc/megaraid/hba0/diskdrives-ch*
Date: Wed, 22 Oct 2008 16:57:40 +0200 [thread overview]
Message-ID: <48FF3F64.4040901@panasas.com> (raw)
In-Reply-To: <48FF3690.2020806@panasas.com>
Boaz Harrosh wrote:
> Yang, Bo wrote:
>> Thanks TOMM. If this is the case, it may affect some of other drivers like our
>> MPT and SAS driver. Is there a way kernel can fix it?
>>
>> Thanks,
>>
>> Bo Yang
>>
>
> Hi Bo Yang
>
> What are the source files for the MPT and SAS drivers from LSI?
> I have made a system wide search for such problems as below and could not
> find any more. But I might have missed them. If you tell me the file names
> I will inspect more closly.
>
> Thanks
> Boaz
In megaraid_sas.c I do not see any places where megasas_cmd->scmd is set
other then at megasas_queue_command() which is the scsi .queue_command
vector. Commands that come from scsi-ml are guarantied to be fully allocated.
Other then that I do not see any places that privately allocate a scsi_cmnd
structure. So I would say megaraid_sas.c should be safe from this bug
Any other files I should inspect?
Boaz
next prev parent reply other threads:[~2008-10-22 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11792-10286@http.bugzilla.kernel.org/>
2008-10-21 19:47 ` [Bugme-new] [Bug 11792] New: Oops when reading /proc/megaraid/hba0/diskdrives-ch* Andrew Morton
2008-10-21 19:54 ` Matthew Wilcox
2008-10-21 20:22 ` Pascal Terjan
2008-10-21 23:08 ` FUJITA Tomonori
2008-10-22 9:04 ` Boaz Harrosh
2008-10-22 9:38 ` FUJITA Tomonori
2008-10-22 10:08 ` Boaz Harrosh
2008-10-22 12:33 ` FUJITA Tomonori
2008-10-22 13:03 ` Yang, Bo
2008-10-22 13:38 ` FUJITA Tomonori
2008-10-22 13:59 ` Yang, Bo
2008-10-22 14:20 ` Boaz Harrosh
2008-10-22 14:57 ` Boaz Harrosh [this message]
2008-10-22 15:57 ` Yang, Bo
2008-10-22 17:31 ` Boaz Harrosh
2008-10-22 13:51 ` Boaz Harrosh
2008-10-23 22:49 ` Pascal Terjan
2008-10-24 0:21 ` FUJITA Tomonori
2008-10-24 13:31 ` Yang, Bo
2008-10-30 13:01 Yang, Bo
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=48FF3F64.4040901@panasas.com \
--to=bharrosh@panasas.com \
--cc=Bo.Yang@lsi.com \
--cc=Sumant.Patro@lsi.com \
--cc=Winston.Austria@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=pterjan@gmail.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