bootm: allow correct bounds-check of destination

While nothing presently examines the destination size, it should at
least be correct so that future users of sys_mapmem() will not be
surprised. Without this, it might be possible to overflow memory.

Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
Kees Cook 2013-08-16 07:59:16 -07:00 committed by Simon Glass
parent ff9d2efdbf
commit 315c0ace7c

View File

@ -368,7 +368,7 @@ static int bootm_load_os(bootm_headers_t *images, unsigned long *load_end,
const char *type_name = genimg_get_type_name(os.type); const char *type_name = genimg_get_type_name(os.type);
load_buf = map_sysmem(load, image_len); load_buf = map_sysmem(load, unc_len);
image_buf = map_sysmem(image_start, image_len); image_buf = map_sysmem(image_start, image_len);
switch (comp) { switch (comp) {
case IH_COMP_NONE: case IH_COMP_NONE: