lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160229163103.00504b12@lxorguk.ukuu.org.uk>
Date:	Mon, 29 Feb 2016 16:31:03 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Ocean HY1 He <hehy1@...ovo.com>
Cc:	"tj@...nel.org" <tj@...nel.org>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] AHCI: Remove conflicting Intel Lewisburg 3rd-party SATA
 RAID device IDs

On Mon, 29 Feb 2016 09:28:19 +0000
Ocean HY1 He <hehy1@...ovo.com> wrote:

> Hi Tejun,
> 
> According to Intel Lewisburg PCH EDS, SATA RAID controller has two types
> of DIDs: RSTe RAID and 3rd Party RAID. RSTe RAID shoud be drived by AHCI
> driver and used to construct MDRAID. These 3rd Party RAID IDs are reserved
> for other 3rd Party RAID drivers for variety.
> 
> So, I think it's a bug to let AHCI driver supporting 3rd Party RAID IDs.
> And it should be ok to remove these existed device IDs.

We have already had this discussion before. I'm surprised it has come
back again, this time via Intel. If Lenovo wants their RAID supported in
Linux then contribute it open source to the kernel. You've been told this
clearly before.

Alan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ