of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch
authorLaura Abbott <lauraa@codeaurora.org>
Fri, 20 Jun 2014 03:13:38 +0000 (20:13 -0700)
committerGrant Likely <grant.likely@linaro.org>
Thu, 26 Jun 2014 16:28:28 +0000 (17:28 +0100)
commita67a6ed15513541579d38bcbd127e7be170710e5
tree571de22898d8ef2ce3f2afdd3cb0873f1ac12477
parenta497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee
of: Check for phys_addr_t overflows in early_init_dt_add_memory_arch

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>
Signed-off-by: Grant Likely <grant.likely@linaro.org>
drivers/of/fdt.c