linux-kernel - Re: [PATCH] genirq: Handle force threading of irqs with primary and thread handler

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]

Date:	Tue, 22 Sep 2015 15:42:38 +0900
From:	Kohji Okuno <okuno.kohji@...panasonic.com>
To:	<tglx@...utronix.de>
CC:	<linux-kernel@...r.kernel.org>, <msmucr@...il.com>,
	<nathan.sullivan@...com>, <bigeasy@...utronix.de>,
	<okuno.kohji@...panasonic.com>
Subject: Re: [PATCH] genirq: Handle force threading of irqs with primary
 and thread handler

From: Thomas Gleixner <tglx@...utronix.de>
Date: Mon, 21 Sep 2015 11:01:10 +0200
> To deal with this proper, we need to force thread the primary handler
> of such interrupts as well. That means that the primary interrupt
> handler is treated as any other primary interrupt handler which is not
> marked IRQF_NO_THREAD. The threaded handler becomes a separate thread
> so the SDHCI flow logic can be handled gracefully.
> 
> The same issue was reported against 4.1-rt.

Hi tglx,
I tried your patch. It worked good for me.

Many thanks,
 Kohji Okuno
--
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/