From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Andrew Goodbody <andrew.goodbody@linaro.org>,
Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Andrew Goodbody <andrew.goodbody@linaro.org>
Subject: Re: [PATCH v4 1/2] cmd: abootimg: Prevent use of unintialised variable
Date: Fri, 27 Jun 2025 08:51:08 +0200 [thread overview]
Message-ID: <878qldy8wz.fsf@kernel.org> (raw)
In-Reply-To: <20250625-abootimg_fix-v4-1-df7af00e87b0@linaro.org>
Hi Andrew,
Thank you for the patch.
On Thu, Jun 26, 2025 at 17:38, Andrew Goodbody <andrew.goodbody@linaro.org> wrote:
> Initiaise vhdr to prevent its use when uninitialised.
s/Initiaise/Initialise/: will fix when applying.
>
> This issue was found with Smatch.
>
> Fixes: 636da2039aea (android: boot: support boot image header version 3 and 4)
> Signed-off-by: Andrew Goodbody <andrew.goodbody@linaro.org>
> ---
> cmd/abootimg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/cmd/abootimg.c b/cmd/abootimg.c
> index ae7a1a7c83b..9ae87581d2c 100644
> --- a/cmd/abootimg.c
> +++ b/cmd/abootimg.c
> @@ -95,7 +95,7 @@ static int abootimg_get_dtb_load_addr(int argc, char *const argv[])
> return CMD_RET_USAGE;
> struct andr_image_data img_data = {0};
> const struct andr_boot_img_hdr_v0 *hdr;
> - const struct andr_vnd_boot_img_hdr *vhdr;
> + const struct andr_vnd_boot_img_hdr *vhdr = NULL;
>
> hdr = map_sysmem(abootimg_addr(), sizeof(*hdr));
> if (get_avendor_bootimg_addr() != -1)
>
> --
> 2.39.5
next prev parent reply other threads:[~2025-06-27 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 16:38 [PATCH v4 0/2] Prevent use of unitialised variable vhdr Andrew Goodbody
2025-06-26 16:38 ` [PATCH v4 1/2] cmd: abootimg: Prevent use of unintialised variable Andrew Goodbody
2025-06-27 6:51 ` Mattijs Korpershoek [this message]
2025-06-26 16:38 ` [PATCH v4 2/2] boot: android: " Andrew Goodbody
2025-06-27 6:52 ` Mattijs Korpershoek
2025-07-02 10:10 ` [PATCH v4 0/2] Prevent use of unitialised variable vhdr Mattijs Korpershoek
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=878qldy8wz.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=andrew.goodbody@linaro.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