linux-kernel - Re: LibPATA code issues / 2.6.17.3 (What is the next step?)

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: <44B7D6CE.4030406@rtr.ca>
Date:	Fri, 14 Jul 2006 13:39:26 -0400
From:	Mark Lord <liml@....ca>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jeff Garzik <jgarzik@...ox.com>, Sander <sander@...ilis.net>,
	linux-kernel@...r.kernel.org,
	IDE/ATA development list <linux-ide@...r.kernel.org>
Subject: Re: LibPATA code issues / 2.6.17.3 (What is the next step?)

Justin Piszcz wrote:
> They are Western Digital 400* drives.
> 
> [4294678.049000]   Vendor: ATA       Model: WDC WD4000KD-00N  Rev: 01.0
> [4294678.050000]   Vendor: ATA       Model: WDC WD4000KD-00N  Rev: 01.0
> 
> On a SiL controller, it also happens when they are on a promise 
> controller too.
> 
> On Fri, 14 Jul 2006, Mark Lord wrote:
> 
>> Justin Piszcz wrote:
>>>
>>> opcode=0x35 & opcode=0xca
>>
>> Those are non-DMA WRITE opcodes.  Using PIO for I/O is pretty rare 
>> these days,
>> so I'm betting that this is not a hard disk device -- compactflash?

Okay.  So why are we issuing PIO WRITE commands to drives that
obviously should only be sent DMA commands by libata?

Perhaps that's the bug.
-
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/