linux-kernel - Re: [PATCH] ata: Add the SW NCQ support to sata

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: <4682211D.4040808@garzik.org>
Date:	Wed, 27 Jun 2007 04:34:37 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Peer Chen <pchen@...dia.com>
CC:	Robert Hancock <hancockr@...w.ca>, kuan luo <kuanluo@...il.com>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Kuan Luo <kluo@...dia.com>
Subject: Re: [PATCH] ata: Add the SW NCQ support to sata_nv for MCP51/MCP55/MCP61

Peer Chen wrote:
> We did the many test with the new version driver and didn't encounter
> that problem, but in certain cases, DMASETUP command packets from drive
> to the controller are corrupted, and the controller issues an R_ERR to
> the drive. Drives that comply with SATA spec will re-transmit the
> corrupted packet and normal operation continues. However, some Maxtor
> NCQ drives do not re-transmit the DMASETUP command packet, resulting in
> software timeout for this command. So if you are using the Maxtor HD and
> meet this problem,please don't enable the NCQ function.

Users should not be expected to know those details, nor be forced to 
suffer discovering this in the field (over and over again for each 
customer).

We have a list of problem devices ata_device_blacklist[] in 
drivers/ata/libata-core.c that should be modified to note each drive 
where NCQ should never be used.

	Jeff


-
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/