linux-kernel - Re: HDD problem, software bug, bios bug, or hardware ?

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: <20120910091732.GB4431@liondog.tnic>
Date:	Mon, 10 Sep 2012 11:17:32 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Mikael Pettersson <mikpe@...uu.se>
Cc:	Adko Branil <adkobranil@...oo.com>,
	Jeff Garzik <jgarzik@...ox.com>,
	linux-ide <linux-ide@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: HDD problem, software bug, bios bug, or hardware ?

On Sun, Sep 02, 2012 at 10:04:53PM +0200, Mikael Pettersson wrote:
> pdc_hard_reset_port needs to serialize because hard reset has to flip
> a port-specific bit in a controller register that's shared by all
> ports, so it takes the host lock. But now an interrupt occurs during
> the hard reset, and pdc_interrupt also has to take the host lock. (I
> don't know why the interrupt occurs, hotplug events are supposed to
> have been masked by ->freeze before ->hardreset. It might come from a
> different device, my test machine has multiple ATA controllers from
> different vendors, and some of them do share IRQ.)

This sounds very fishy - could it be the hardware raising a spurious IRQ
or something although it shouldn't?

Thanks.

-- 
Regards/Gruss,
    Boris.
--
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/