From: Linus Walleij <linus.walleij@linaro.org>
To: Russell King <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
kernel test robot <lkp@intel.com>
Subject: [PATCH] ARM: mmu: Declare section start/end correctly
Date: Thu, 17 Jun 2021 12:01:52 +0200 [thread overview]
Message-ID: <20210617100152.788532-1-linus.walleij@linaro.org> (raw)
The kernel test robot reported an interesting bug:
A debug print was using %08x with kernel_sec_start and kernel_sec_end being
phys_addr_t which can be either u32 or u64 (possibly more).
Actually these should just be declared as u32 to begin with: they are declared
as such in the assembly in head.S and the kernel definately boots in a 32 bit
physical address space. Redeclare the kernel_sec_start and kernel_sec_end
to rid the bug.
Reported-by: kernel test robot <lkp@intel.com>
Fixes: 6e121df14ccd ("ARM: 9090/1: Map the lowmem and kernel separately")
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/arm/include/asm/memory.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/include/asm/memory.h b/arch/arm/include/asm/memory.h
index ca213d7d095f..cfc9dfd70aad 100644
--- a/arch/arm/include/asm/memory.h
+++ b/arch/arm/include/asm/memory.h
@@ -162,8 +162,8 @@ extern unsigned long vectors_base;
* Physical start and end address of the kernel sections. These addresses are
* 2MB-aligned to match the section mappings placed over the kernel.
*/
-extern phys_addr_t kernel_sec_start;
-extern phys_addr_t kernel_sec_end;
+extern u32 kernel_sec_start;
+extern u32 kernel_sec_end;
/*
* Physical vs virtual RAM address space conversion. These are
--
2.31.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2021-06-17 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210617100152.788532-1-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).