From: Patrick Wildt <patrick@blueri.se>
To: u-boot@lists.denx.de
Subject: [PATCH] ARM: imx: hab: panic on authentication failure
Date: Sat, 30 May 2020 22:14:57 +0200 [thread overview]
Message-ID: <20200530201457.GA8838@ryzen.blueri.se> (raw)
In-Reply-To: <CAOMZO5AC+TJpBrtEPxPbDzVPsvOnJu7N8w-7TTDp_uoJ2_xKDA@mail.gmail.com>
On Sat, May 30, 2020 at 03:31:29PM -0300, Fabio Estevam wrote:
> Hi Marek,
>
> [Adding Breno]
>
> On Sat, May 30, 2020 at 3:29 PM Marek Vasut <marex@denx.de> wrote:
> >
> > Instead of hang()ing the system and thus disallowing any automated
> > recovery possibility from a HAB authentication failure, panic() .
> > The panic() function can be configured to hang() the system after
> > printing an error message, however the default is to reset the
> > system instead.
> >
> > This allows redundant boot to work correctly. In case the primary
> > or secondary image cannot be authenticated, the system reboots and
> > bootrom can try to start the other one.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Fabio Estevam <festevam@gmail.com>
> > Cc: NXP i.MX U-Boot Team <uboot-imx@nxp.com>
> > Cc: Peng Fan <peng.fan@nxp.com>
> > Cc: Stefano Babic <sbabic@denx.de>
>
> This is a better behavior indeed:
>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
What about this? Have you ignored this patch for a reason? :/
https://marc.info/?l=u-boot&m=159069441005730&w=2
next prev parent reply other threads:[~2020-05-30 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 18:29 [PATCH] ARM: imx: hab: panic on authentication failure Marek Vasut
2020-05-30 18:31 ` Fabio Estevam
2020-05-30 20:14 ` Patrick Wildt [this message]
2020-05-30 20:29 ` Marek Vasut
2020-05-30 20:53 ` Patrick Wildt
2020-05-31 15:38 ` Marek Vasut
2020-05-31 15:53 ` Patrick Wildt
2020-05-31 16:51 ` Marek Vasut
2020-05-31 17:02 ` Patrick Wildt
2020-08-04 8:52 ` sbabic at denx.de
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=20200530201457.GA8838@ryzen.blueri.se \
--to=patrick@blueri.se \
--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