linux-kernel - Re: [PATCH V4 04/14] genirq: Generic chip: Add big endian I/O accessors

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: <7hy4riogwt.fsf@deeprootsystems.com>
Date:	Mon, 10 Nov 2014 14:00:02 -0800
From:	Kevin Hilman <khilman@...nel.org>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	tglx@...utronix.de, jason@...edaemon.net, linux-sh@...r.kernel.org,
	arnd@...db.de, f.fainelli@...il.com, ralf@...ux-mips.org,
	sergei.shtylyov@...entembedded.com, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, mbizon@...ebox.fr, jogo@...nwrt.org,
	linux-mips@...ux-mips.org, nicolas.ferre@...el.com,
	alexandre.belloni@...e-electrons.com,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH V4 04/14] genirq: Generic chip: Add big endian I/O accessors

Kevin Cernekee <cernekee@...il.com> writes:

> Use io{read,write}32be if the caller specified IRQ_GC_BE_IO when creating
> the irqchip.
>
> Signed-off-by: Kevin Cernekee <cernekee@...il.com>

I bisected a couple ARM boot failures in next-20141110 on atmel sama5 platforms down to
this patch, though I'm not quite yet sure how it's causing the failure.
I'm not getting any console output, so haven't been able to dig deeper
yet.  Maybe the atmel maintainers (Cc'd) can help dig.

I've confirmed that reverting $SUBJECT patch (commit
b79055952badbd73710685643bab44104f2509ea2) on top of next-20141110 gets
things booting again.

Also, it only happens with sama5_defconfig, not with multi_v7_defconfig.

Kevin

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