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: <alpine.LFD.2.02.1109142149060.2723@ionos>
Date:	Wed, 14 Sep 2011 21:50:19 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Tero Kristo <t-kristo@...com>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] irq: call also chip->irq_mask from irq_disable

On Wed, 14 Sep 2011, Tero Kristo wrote:
> On Wed, 2011-09-14 at 18:04 +0200, Thomas Gleixner wrote:
> > What are you trying to solve ?
> 
> I was seeing a hang with a chain handler implementation that was caused
> by this delayed disable implementation, I am using a generic chip with
> irq_mask / irq_unmask. Adding this patch to the kernel fixed the hang in
> this case. There might be something wrong in my implementation of the
> chain handler itself, I'll take a look at it again and try to figure out
> another way to avoid it. I have another idea I can pursue, and based on
> some initial testing it actually seems to be working.

chained handlers are not subject to disable/enable_irq usually. Care
to share the code ?

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ