U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>,
	Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
	Sam Edwards <cfsworks@gmail.com>, Anshul Dalal <anshuld@ti.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] spl: fix error handling in spl_fit_get_image_name()
Date: Tue, 24 Jun 2025 19:00:09 -0700	[thread overview]
Message-ID: <7025bab8-117b-414d-9bb9-78288681fec2@freeshell.de> (raw)
In-Reply-To: <20250624153431.46986-1-heinrich.schuchardt@canonical.com>

Hi Heinrich,

On 6/24/25 08:34, Heinrich Schuchardt wrote:
> spl_fit_get_image_name() used to lack a detection of malformed image name
> properties in FIT images. The change in commit 3704b888a4ca ("common/spl:
> fix potential out of buffer access in spl_fit_get_image_name function")
> tried to fix this  but led to function spl_fit_get_image_name() no longer
> detecting if a property at index > 1 does not exist.
> 
> This patch is reverted.
> 
> An explicit check for malformed image name properties is introduced.
> 
> Cf.
> [BUG] [PATCH v5 1/3] common/spl: fix potential out of buffer access in
> spl_fit_get_image_name function
> https://lore.kernel.org/u-boot/38f5d078-3328-4bdb-9c95-4fb5fe89ddc2@gmx.de/T/#u
> 
> Heinrich Schuchardt (2):
>   common/spl: Revert fix potential out of buffer access in
>     spl_fit_get_image_name function
>   common/spl: guard against buffer overflow in spl_fit_get_image_name()
> 
>  common/spl/spl_fit.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 

Before:
U-Boot SPL 2025.07-rc4-00030-g0daf2d0cabef (Jun 22 2025 - 23:27:44 -0700)
DDR version: dc2e84f0.
Trying to boot from SPI
cannot find image node '': -1

OpenSBI v1.6

After:
U-Boot SPL 2025.07-rc4-00032-g562b7d099d46 (Jun 24 2025 - 18:53:15 -0700)
DDR version: dc2e84f0.
Trying to boot from SPI

OpenSBI v1.6

For the series,

Tested-By: E Shattow <e@freeshell.de>

  parent reply	other threads:[~2025-06-25  2:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24 15:34 [PATCH 0/2] spl: fix error handling in spl_fit_get_image_name() Heinrich Schuchardt
2025-06-24 15:34 ` [PATCH 1/2] common/spl: Revert fix potential out of buffer access in spl_fit_get_image_name function Heinrich Schuchardt
2025-06-25  2:18   ` E Shattow
2025-06-24 15:34 ` [PATCH 2/2] common/spl: guard against buffer overflow in spl_fit_get_image_name() Heinrich Schuchardt
2025-06-24 21:02   ` Mikhail Kshevetskiy
2025-06-24 23:05     ` Heinrich Schuchardt
2025-06-24 21:05   ` Mikhail Kshevetskiy
2025-06-24 23:05     ` Heinrich Schuchardt
2025-06-24 23:07       ` Mikhail Kshevetskiy
2025-06-25  2:18   ` E Shattow
2025-06-25  2:00 ` E Shattow [this message]
2025-06-26 19:32 ` [PATCH 0/2] spl: fix error handling " Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2025-06-24 14:51 Heinrich Schuchardt

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=7025bab8-117b-414d-9bb9-78288681fec2@freeshell.de \
    --to=e@freeshell.de \
    --cc=anshuld@ti.com \
    --cc=cfsworks@gmail.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=mikhail.kshevetskiy@iopsys.eu \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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