linux-kernel - Re: [PATCH] genirq: Fix bad IRQ

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: <20150920.003356.1191254663935857851.okuno.kohji@jp.panasonic.com>
Date:	Sun, 20 Sep 2015 00:33:56 +0900
From:	Kohji Okuno <okuno.kohji@...panasonic.com>
To:	<tglx@...utronix.de>
CC:	<marc.zyngier@....com>, <linux-kernel@...r.kernel.org>,
	<okuno.kohji@...panasonic.com>
Subject: Re: [PATCH] genirq: Fix bad IRQ_ONSHOT in forced IRQ setting

From: Thomas Gleixner <tglx@...utronix.de>
Date: Fri, 18 Sep 2015 16:46:24 +0200
> On Fri, 18 Sep 2015, Kohji Okuno wrote:
>> 
>> irq thread(runs sdhci_thread_irq()) is waiting on
>> drivers/mmc/core/core.c:mmc_wait_for_req_done() in order to access
>> a SDIO register. And, this thread shoud be woken up from
>> sdhci_irq() after the completion of the register access.
>> But, since the IRQ is masked, sdhci_irq() is not called and  irq
>> thread can not wake up. This is root cause, I think.
>> What do you think about this?
> 
> Ah, that explains it. Let me think about it a bit.
> 
> Thanks,
> 
> 	tglx

If something is not clear please let me know.
By the way, even if other issue exists, we should change
irq_setup_forced_threading() as my patch, I think.

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/