linux-kernel - Re: Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable workaround

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2009 14:35:39 +0200
From:	Michael Roth <mroth@...sie.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	petkovbb@...il.com, petkovbb@...glemail.com,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable
 workaround

>> take it ok. Also, if I remember correctly, the original ide-cd behavior
>> was to issue the command and _then_ start DMA so we're back to that. I
>> guess now we should be concerned whether the other ATAPI devices can
>> handle the reverse situation where you first issue a command and _then_
>> start DMA.. Hmm...
> 
> Most devices don't care but you do need to follow the exact ATAPI spec.
> If you search way back through the archives you'll find long discussions
> on this during either 2.4 or 2.2 when HP hit problems caused by us
> turning DMA on too early.

AFAIK, the old bevavior was to start DMA _after_ issuing the command _only_
for CD-drives and for the remaining ide devices the other way around,
why not just restore the old behavior and do the DMA after command only
for CD-drives?


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