public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] imximage: header.length of 4 is valid
Date: Tue, 6 Oct 2015 11:09:33 -0700	[thread overview]
Message-ID: <56140E5D.2030700@boundarydevices.com> (raw)
In-Reply-To: <5613B0F3.80406@denx.de>

On 10/6/2015 4:30 AM, stefano babic wrote:
> Hi Troy,
> 
> Am 06.10.2015 um 00:17 schrieb Troy Kisky:
>> On 9/21/2015 2:02 PM, Troy Kisky wrote:
>>> Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
>>> ---
>>>  tools/imximage.c | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/tools/imximage.c b/tools/imximage.c
>>> index 97a6880..7c21922 100644
>>> --- a/tools/imximage.c
>>> +++ b/tools/imximage.c
>>> @@ -396,8 +396,8 @@ static void print_hdr_v2(struct imx_header *imx_hdr)
>>>  	dcd_v2_t *dcd_v2 = &hdr_v2->dcd_table;
>>>  	uint32_t size, version;
>>>  
>>> -	size = be16_to_cpu(dcd_v2->header.length) - 8;
>>> -	if (size > (MAX_HW_CFG_SIZE_V2 * sizeof(dcd_addr_data_t))) {
>>> +	size = be16_to_cpu(dcd_v2->header.length);
>>> +	if (size > (MAX_HW_CFG_SIZE_V2 * sizeof(dcd_addr_data_t)) + 8) {
>>>  		fprintf(stderr,
>>>  			"Error: Image corrupt DCD size %d exceed maximum %d\n",
>>>  			(uint32_t)(size / sizeof(dcd_addr_data_t)),
>>>
>> Hi Stefano,
>>
>>
>> Are there outstanding concerns about applying this patch and then
>> applying
>>
>> imximage: fix commands other than write_data
>>
>> Where you replied
>> "This patch breaks building boards with SPL:
>>
>> Building current source for 85 boards (6 threads, 1 job per thread)
>>        arm:  +   colibri_vf_dtb
>> +Error: Image corrupt DCD size 536870911 exceed maximum 220
>> +make[2]: *** [u-boot-dtb.imx] Error 1
>> +make[1]: *** [u-boot-dtb.imx] Error 2
>> +make: *** [sub-make] Error 2
>>        arm:  +   mx6sabresd_spl
>> +Error: Image corrupt DCD size 536870911 exceed maximum 220
>> "
>>
>>
>> Or would you rather that I squash them together?
> 
> Yes, please do it - I would like to avoid issues by git bisect.
> 


That is not an issue if you apply "imximage: header.length of 4 is valid" first.

Would you still like it squashed, or a new series, or just use the previous patches ?


Troy

  reply	other threads:[~2015-10-06 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 21:02 [U-Boot] [PATCH 1/1] imximage: header.length of 4 is valid Troy Kisky
2015-10-05 23:17 ` Troy Kisky
2015-10-06 11:30   ` stefano babic
2015-10-06 18:09     ` Troy Kisky [this message]
2015-10-07  8:01       ` Stefano Babic
2015-10-07 12:03 ` Stefano Babic

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=56140E5D.2030700@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=u-boot@lists.denx.de \
    /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