From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [PATCH v3 2/5] mkimage: fit_image: handle multiple errors when writing signatures
Date: Fri, 19 Jun 2020 12:47:01 +0200 [thread overview]
Message-ID: <8657654.VsHI1tnm3i@phil> (raw)
In-Reply-To: <CAPnjgZ3hyh-CoOfu7kbeKrbA91zH9_n=RK7KQksJ-CaFv0srWA@mail.gmail.com>
Am Sonntag, 31. Mai 2020, 16:07:56 CEST schrieb Simon Glass:
> Hi Heiko,
>
> On Tue, 26 May 2020 at 04:44, Heiko Stuebner <heiko@sntech.de> wrote:
> >
> > From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> >
> > fit_image_write_sig() contains mostly functions from libfdt that
> > return FDT_ERR_foo errors but also a call to fit_set_timestamp()
> > which returns a regular error.
> >
> > When handling the size increase via multiple iterations, check
> > for both -FDT_ERR_NOSPACE but also for -ENOSPC.
> >
> > There is no real conflict, as FDT_ERR_NOSPACE = 3 = ESRCH
> > (No such process) and ENOSPC = 28 which is above any FDT_ERR_*.
> >
> > Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> > Reviewed-by: Simon Glass <sjg@chromium.org>
> > Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
> > ---
> > tools/image-host.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Changing my mind on this - I wonder if we can change
> fit_image_write_sig() to always return an errno code, never an FDT
> code? Could be a follow-on patch.
I'll take that suggestion and do a followup with this suggestion,
simply because this may open up additional discussion.
Heiko
> > diff --git a/tools/image-host.c b/tools/image-host.c
> > index 9a83b7f675..baf9590f3b 100644
> > --- a/tools/image-host.c
> > +++ b/tools/image-host.c
> > @@ -241,7 +241,7 @@ static int fit_image_process_sig(const char *keydir, void *keydest,
> > ret = fit_image_write_sig(fit, noffset, value, value_len, comment,
> > NULL, 0, cmdname);
> > if (ret) {
> > - if (ret == -FDT_ERR_NOSPACE)
> > + if (ret == -FDT_ERR_NOSPACE || ret == -ENOSPC)
> > return -ENOSPC;
> > printf("Can't write signature for '%s' signature node in '%s' conf node: %s\n",
> > node_name, image_name, fdt_strerror(ret));
> > --
> > 2.25.1
> >
>
> Regards,
> Simon
>
next prev parent reply other threads:[~2020-06-19 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 10:44 [PATCH v3 0/5] rockchip: make it possible to sign the u-boot.itb Heiko Stuebner
2020-05-26 10:44 ` [PATCH v3 1/5] imx: mkimage_fit_atf: Fix FIT image if BL31.bin missing Heiko Stuebner
2020-05-26 12:53 ` Peng Fan
2020-05-26 10:44 ` [PATCH v3 2/5] mkimage: fit_image: handle multiple errors when writing signatures Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-06-19 10:47 ` Heiko Stuebner [this message]
2020-05-26 10:44 ` [PATCH v3 3/5] spl: fit: enable signing a generated u-boot.itb Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-05-26 10:44 ` [PATCH v3 4/5] spl: fit: add Kconfig option to specify key-hint for fit_generator Heiko Stuebner
2020-05-26 10:44 ` [PATCH v3 5/5] rockchip: make_fit_atf: add signature handling Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-05-31 8:28 ` [PATCH v3 0/5] rockchip: make it possible to sign the u-boot.itb Kever Yang
2020-06-19 10:47 ` Heiko Stuebner
2020-06-26 1:12 ` Simon Glass
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=8657654.VsHI1tnm3i@phil \
--to=heiko@sntech.de \
--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