linux-kernel - RE: [PATCH] genirq: Add the IRQS_ONESHOT support for edge interrupt

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <27240C0AC20F114CBF8149A2696CBE4A182055@SHSMSX101.ccr.corp.intel.com>
Date:	Tue, 18 Sep 2012 07:18:37 +0000
From:	"Liu, Chuansheng" <chuansheng.liu@...el.com>
To:	anish singh <anish198519851985@...il.com>
CC:	"'linux-kernel@...r.kernel.org' (linux-kernel@...r.kernel.org)" 
	<linux-kernel@...r.kernel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>
Subject: RE: [PATCH] genirq: Add the IRQS_ONESHOT support for edge interrupt

> Are you sure you have not returned from the irq_thread and how do you
> know that primary handler is called in between when your irq_thread is
> running?

I am sure because the spin recursive locks has been printed with call stack,
further more, with IRQS_ONESHOT, I have printed the value of irqd_irq_masked(&desc->irq_data),
it is 0, that means when with IRQS_ONESHOT, and the irq thread is called but the irq is not masked during this time.