linux-kernel - Re: Where is the interrupt going?

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: <20071122021422.GA9265@fattire.cabal.ca>
Date:	Wed, 21 Nov 2007 21:14:22 -0500
From:	Kyle McMartin <kyle@...artin.ca>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Al Niessner <Al.Niessner@....nasa.gov>,
	linux-kernel@...r.kernel.org
Subject: Re: Where is the interrupt going?

On Thu, Nov 22, 2007 at 01:56:25AM +0000, Alan Cox wrote:
> > status = request_irq (apcsi[i].board_irq,
> >                                       apc8620_handler,
> >                                       IRQF_DISABLED,
> 
> You set IRQF_DISABLED
> 
> Do you then enable the interrupt anywhere later on ?
> 

IRQF_DISABLED just means that the handler is atomic wrt other local
interrupts. Shouldn't be the cause of this.

cheers,
	Kyle
-
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/