linux-kernel - Re: IRQ enable/disable BUG in IDE w/shared IRQs

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: <4D309981.5030107@garzik.org>
Date:	Fri, 14 Jan 2011 13:44:17 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	David Miller <davem@...emloft.net>, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org, marvin@...atex.cz
Subject: Re: IRQ enable/disable BUG in IDE w/shared IRQs

On 01/14/2011 05:30 AM, Thomas Gleixner wrote:
> On Thu, 13 Jan 2011, David Miller wrote:
>> I have a hard time believing we've gotten away with this for so long.
>> Maybe it really is that rare to share the IDE interrupts with other
>> stuff?
>
> IIRC, the legacy IDE interrupts were 14/15 and those were never shared.

Yes, non-shared 14/15 were the 95% common case for the longest time. 
Sharing IDE interrupts within old-IDE worked FSVO "working", but the 
interrupt probes were written for a non-shared interrupt, then hacking 
into working for shared interrupts when PCI first starting showing up on 
the scene.

	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/