From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
Date: Thu, 1 Aug 2019 21:06:32 +0200
Subject: [U-Boot] fit image: boot gzipped ramdisk does not work anymore
In-Reply-To: <CAODwPW9A5SAm72yODOJtCxjnmzkz3JhcQQtW4zK1k0hAP79RdA@mail.gmail.com>
References: <017cf623-d470-cb72-c753-824236b63f43@denx.de>
 <6e972a84-2a18-74df-2575-60144381a635@gmail.com>
 <7543a771-efd5-72cd-6f91-ee6d0863b21c@denx.de>
 <20190801155846.GF6403@bill-the-cat>
 <CAODwPW_36Q=M7WshCZGkk7VuwbKRngX2P128UdhNn-ApyoPMnQ@mail.gmail.com>
 <a01e07e5-6596-6d88-2f58-1b61be5816ae@gmail.com>
 <CAODwPW9A5SAm72yODOJtCxjnmzkz3JhcQQtW4zK1k0hAP79RdA@mail.gmail.com>
Message-ID: <d89c4903-3b3c-0c94-6698-91bd6cc64b9f@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Am 01.08.2019 um 21:01 schrieb Julius Werner:
>> Well, I'm sure you'd find enough FIT images where the uncompression
>> might succeed but the target space for decompression is not big enough
>> (see bootm_size), would such an error be fixed as well?
> 
> I think so? Assuming all the compression algorithms check for an
> output buffer overrun (looks like they do), that should also just lead
> to a compression error and go into the fallback path.

Then I think that would be the best way to start and see if it's good 
enough for backwards compatibility.

Regards,
Simon