From: grant.likely@linaro.org (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch
Date: Tue, 24 Jun 2014 12:19:55 +0100 [thread overview]
Message-ID: <20140624111955.3F4E8C40B13@trevor.secretlab.ca> (raw)
In-Reply-To: <alpine.LFD.2.11.1406192329400.16842@knanqh.ubzr>
On Thu, 19 Jun 2014 23:33:27 -0400 (EDT), Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> On Thu, 19 Jun 2014, Laura Abbott wrote:
>
> > The common early_init_dt_add_memory_arch takes the base and size
> > of a memory region as u64 types. The function never checks if
> > the base and size can actually fit in a phys_addr_t which may
> > be smaller than 64-bits. This may result in incorrect memory
> > being passed to memblock_add if the memory falls outside the
> > range of phys_addr_t. Add range checks for the base and size if
> > phys_addr_t is smaller than u64.
> >
> > Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
>
> Acked-by: Nicolas Pitre <nico@linaro.org>
Applied, thanks.
g.
>
> > ---
> > v2: Switched to sizeof(phys_addr_t) < sizeof(u64) instead of macros.
> > Sending to right e-mails/mailing lists this time.
> >
> > drivers/of/fdt.c | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> > index c4cddf0..b777d8f 100644
> > --- a/drivers/of/fdt.c
> > +++ b/drivers/of/fdt.c
> > @@ -880,6 +880,21 @@ void __init __weak early_init_dt_add_memory_arch(u64 base, u64 size)
> > const u64 phys_offset = __pa(PAGE_OFFSET);
> > base &= PAGE_MASK;
> > size &= PAGE_MASK;
> > +
> > + if (sizeof(phys_addr_t) < sizeof(u64)) {
> > + if (base > ULONG_MAX) {
> > + pr_warning("Ignoring memory block 0x%llx - 0x%llx\n",
> > + base, base + size);
> > + return;
> > + }
> > +
> > + if (base + size > ULONG_MAX) {
> > + pr_warning("Ignoring memory range 0x%lx - 0x%llx\n",
> > + ULONG_MAX, base + size);
> > + size = ULONG_MAX - base;
> > + }
> > + }
> > +
> > if (base + size < phys_offset) {
> > pr_warning("Ignoring memory block 0x%llx - 0x%llx\n",
> > base, base + size);
> > --
> > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> > hosted by The Linux Foundation
> >
prev parent reply other threads:[~2014-06-24 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 3:13 [PATCHv2] of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch Laura Abbott
2014-06-20 3:33 ` Nicolas Pitre
2014-06-24 11:19 ` Grant Likely [this message]
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=20140624111955.3F4E8C40B13@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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