linux-kernel - Re: [GIT pull] irq updates for 4.3

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:	Mon, 31 Aug 2015 09:47:37 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Thomas Gleixner <tglx@...utronix.de>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Marc Zyngier <marc.zyngier@....com>
Subject: Re: [GIT pull] irq updates for 4.3

On 08/31/2015 09:12 AM, Stephen Rothwell wrote:
> Hi Thomas,
>
> On Mon, 31 Aug 2015 12:04:37 +0200 (CEST) Thomas Gleixner <tglx@...utronix.de> wrote:
>>
>> Marc Zyngier (23):
>>        irqchip/GIC: Convert to EOImode == 1
>
> This appears to lead to qemu arm boot tests silently failing (according
> to Guenter).  This commit only appeared in next-20150831.
>

I think we really need more time between patches showing up in -next and
being pushed upstream. We have several new failures in -next which were
introduced after next-20150828, with this being the most serious one.

Of course, that additional time doesn't help if failures in -next are
known for weeks and still end up in mainline. Not really sure how
to solve that problem.

Guenter

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