linux-kernel - RE: [PATCH] Add quirk to set AHCI mode on ICH boards

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <F72FA20C31DD4F4C997B91C5B3690A095054A7@hqemmail07.nvidia.com>
Date:	Wed, 14 Nov 2007 10:35:26 -0800
From:	"Allen Martin" <AMartin@...dia.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Jeff Garzik" <jeff@...zik.org>, "Mark Lord" <liml@....ca>,
	"Riki Oktarianto" <rkoktarianto@...il.com>,
	<linux-kernel@...r.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@...e.de>, <linux-ide@...r.kernel.org>
Subject: RE: [PATCH] Add quirk to set AHCI mode on ICH boards

> > What I'm worred about is SMI traps implemented in the SBIOS for AHCI
> > workarounds that may be disabled when in IDE mode.
> 
> For Nvidia devices those would only be present if there were problems
> with the AHCI hardware right, which would mean you could 
> simply tell us
> what workarounds to implement.

Errata for which there is an SBIOS workaround are generally only
released to BIOS vendors and under NDA.  If Linux users were impacted by
such a bug we would most likely release a patch, but a much more likely
scenario is that it slips through the cracks because it's not a
configuration we would test in our QA.  So a small minority of users
that are running AHCI in class code 0101 would get some very rare but
serious errors that would be impossible to debug.

> > I believe most of the issues with sata_nv have been due to lack of
> > documentation of ADMA and swNCQ.  The NVIDA AHCI controllers that
> 
> I am glad Nvidia accept this point. It would be nice to see it fixed.

I don't have any say over that, but it's probably unlikely to be fixed.
Going forward we're only using open standards for storage.

-Allen
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/