public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Michael Walle" <mwalle@kernel.org>
To: "Tom Rini" <trini@konsulko.com>
Cc: "Simon Glass" <sjg@chromium.org>, "Marek Vasut" <marex@denx.de>,
	<u-boot@lists.denx.de>
Subject: Re: [PATCH] common/spl: fix endless loop in spl_fit_append_fdt()
Date: Fri, 31 Oct 2025 14:13:33 +0100	[thread overview]
Message-ID: <DDWJ8Q2MPP5D.2HMK9EU3A220O@kernel.org> (raw)
In-Reply-To: <20251027230358.GD6688@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

On Tue Oct 28, 2025 at 12:03 AM CET, Tom Rini wrote:
> On Mon, Oct 27, 2025 at 12:05:21PM +0100, Michael Walle wrote:
>
>> Technically, commit 24bf44cf88e7 ("spl: fit: Do not fail immediately if
>> an overlay is not available") introduced that regression as the code
>> will never advance if spl_fit_get_image_name() will return an error. But
>> at that time, spl_fit_get_image_node() was used in spl_fit_append_fdt()
>> which calls fdt_subnode_offset() to get the image node. And I presume
>> the commit was about the latter failing gracefully and trying the next
>> one.
>> 
>> But with commit b13eaf3bb4e6 ("spl: fit: Add board level function to
>> decide application of DTO") that behavior changed and the loop in
>> spl_fit_append_fdt() no longer uses spl_fit_get_image_node() but
>> spl_fit_get_image_name() directly. Thus it doesn't make any sense to not
>> break the loop if that fails.
>> 
>> Also, the original use case of commit 24bf44cf88e7 ("spl: fit: Do not
>> fail immediately if an overlay is not available") is preserved because
>> spl_subnode_offset() is now called within the loop and errors are
>> handled gracefully (and advancing the index).
>> 
>> Fixes: b13eaf3bb4e6 ("spl: fit: Add board level function to decide application of DTO")
>> Signed-off-by: Michael Walle <mwalle@kernel.org>
>
> Thanks for explaining what's going on in such detail.
>
> Reviewed-by: Tom Rini <trini@konsulko.com>

Please don't pick this up. There will be a v2 as this is breaking
any subsequent code in the loop.

-michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

      reply	other threads:[~2025-10-31 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-27 11:05 [PATCH] common/spl: fix endless loop in spl_fit_append_fdt() Michael Walle
2025-10-27 23:03 ` Tom Rini
2025-10-31 13:13   ` Michael Walle [this message]

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=DDWJ8Q2MPP5D.2HMK9EU3A220O@kernel.org \
    --to=mwalle@kernel.org \
    --cc=marex@denx.de \
    --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