[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yl8GInPZyl2PqK7D@shell.armlinux.org.uk>
Date: Tue, 19 Apr 2022 19:57:38 +0100
From: "Russell King (Oracle)" <linux@...linux.org.uk>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ardb@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
max.krummenacher@...adex.com, Shawn Guo <shawnguo@...nel.org>,
Stefano Stabellini <stefano.stabellini@...inx.com>,
Christoph Hellwig <hch@....de>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [next] arm: boot failed - PC is at cpu_ca15_set_pte_ext
On Tue, Apr 19, 2022 at 04:28:52PM +0530, Naresh Kamboju wrote:
> Linux next 20220419 boot failed on arm architecture qemu_arm and BeagleBoard
> x15 device.
Was the immediately previous linux-next behaving correctly?
If so, nothing has changed in the ARM32 kernel tree, so this must be
someone else's issue - code that someone else has pushed into
linux-next.
It looks to me like someone is walking the page tables incorrectly,
somewhere buried in handle_mm_fault(), because the PTE pointer is in
the upper-2k of a 4k page, which is most definitely illegal on arm32.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Powered by blists - more mailing lists