From: "Darrick J. Wong" <djwong@us.ibm.com>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serverworks should not take ahold of megaraid'd controllers
Date: Fri, 22 Jul 2005 16:17:15 -0700 [thread overview]
Message-ID: <42E17E7B.6090805@us.ibm.com> (raw)
In-Reply-To: <1121993194.854.14.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Arjan, Alan:
I didn't know that dmraid supports MegaIDE nowadays. Thanks for the
tipoff, and I apologize for the unnecessary traffic. I'll look into dmraid.
--D
Alan Cox wrote:
> On Iau, 2005-07-21 at 15:37 -0700, Darrick J. Wong wrote:
>
>>I've noticed what might be a small bug with the serverworks driver in
>>2.6.12.3. The IBM HS20 blade has a ServerWorks CSB6 IDE controller with
>>an optional LSI MegaIDE RAID BIOS (BIOS assisted software raid, iow).
>
>
> With a binary only proprietary driver.
>
>
>>(ServerWorks) to IBM. However, the serverworks driver doesn't notice
>>this and will attach to the controller anyway, thus allowing raw access
>>to the disks in the RAID. An unsuspecting user can then read and write
>>whatever they want to the drive, which could very well degrade or
>>destroy the array, which is clearly not desirable behavior.
>
>
> It may be appropriate for some vendor situations but it isn't
> appropriate for the base kernel to default to assuming the user wants to
> use binary only drivers instead of dmraid. Especially as the raid
> formats for this hardware are partially known despite no assistance I
> know of from the vendor.
>
> Alan
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-07-22 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 22:37 [PATCH] serverworks should not take ahold of megaraid'd controllers Darrick J. Wong
2005-07-21 22:51 ` Arjan van de Ven
2005-07-22 0:46 ` Alan Cox
2005-07-22 23:17 ` Darrick J. Wong [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=42E17E7B.6090805@us.ibm.com \
--to=djwong@us.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.