linux-kernel - Re: [BUG] sdhci regression in 2.6.21-rc2

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: <45EC3609.4030809@drzeus.cx>
Date:	Mon, 05 Mar 2007 16:23:53 +0100
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Mark Lord <lkml@....ca>
CC:	sdhci-devel@...t.drzeus.cx, Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] sdhci regression in 2.6.21-rc2

Pierre Ossman wrote:
> Mark Lord wrote:
>> But.. in the middle of all of this, we now see the SHDCI code
>> trying to talk to its as-yet-not-restored device, and being rather
>> noisy about it all:
>>
> 
> Not quite. I'd say it's the kernel calling the interrupt handler of a
> currently sleeping device. Since we're seeing this problem I assume the
> kernel's interrupt code isn't aware of PM states?
> 

Hmm... I guess it can't be as the interrupt handler isn't associated with a
device, just a random pointer.

So either release the interrupt (which seems a bit unsafe as then we might not
get it back), or handle states at the start of the isr.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org
-
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/