linux-kernel - Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a guest")

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.DEB.2.11.1509161851330.3951@nanos>
Date:	Wed, 16 Sep 2015 18:52:41 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jisheng Zhang <jszhang@...vell.com>
cc:	jason@...edaemon.net, linux-arm-kernel@...ts.infradead.org,
	marc.zyngier@....com, linux-kernel@...r.kernel.org
Subject: Re: Regression by 01f779f4862b ("irqchip/GIC: Don't deactivate
 interrupts forwarded to a guest")

On Thu, 17 Sep 2015, Jisheng Zhang wrote:

> Hi Marc,
> 
> Commit 01f779f4862b ("irqchip/GIC: Don't deactivate interrupts forwarded to a
> guest") causes a regression on Marvell BG4CT SoC. In this SoC, there's only one
> GIC, the secondary irq controller is Synopsys DW iCtl:
> drivers/irqchip/irq-dw-apb-ictl.c
> 
> So cascading_gic_irq() should return true on Marvell BG4CT SoC, but it returns
> false. The logic in cascading_gic_irq() doesn't take cascaded irq controller
> which is provided by non-gic controllers.

I have a fix pending for this in

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tmp.irq

714665351cc7: irqchip/gic: Use IRQD_FORWARDED_TO_VCPU flag

Can you please give that a try?

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/