public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] test: efi_selftest: Do not force serial# setting
Date: Fri, 7 Aug 2020 16:12:43 -0400	[thread overview]
Message-ID: <20200807201243.GB20605@bill-the-cat> (raw)
In-Reply-To: <ae946532-df74-5e48-3346-ad16df8dc2df@gmx.de>

On Fri, Aug 07, 2020 at 09:56:58PM +0200, Heinrich Schuchardt wrote:
> On 8/7/20 9:50 PM, Tom Rini wrote:
> > On Fri, Aug 07, 2020 at 09:34:06PM +0200, Heinrich Schuchardt wrote:
> >
> >> On 7/31/20 11:42 PM, Tom Rini wrote:
> >>> On Fri, Jul 31, 2020 at 10:12:32AM -0400, Tom Rini wrote:
> >>>
> >>>> As part of the EFI self test we set and check the serial# variable.
> >>>> However, we should not be forcing this setting.  In the case where we
> >>>> are allowed to change the variable it will change, and we will pass the
> >>>> test.  In the case where we cannot change it, force may or may not be
> >>>> allowed, depending on further environment restrictions.  Drop the -f
> >>>> flag here as we do not need it.
> >>>>
> >>>> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >>>> Signed-off-by: Tom Rini <trini@konsulko.com>
> >>>
> >>> Applied to u-boot/master, thanks!
> >>>
> >>
> >>
> >> With this patch on the Pine64 LTS:
> >>
> >> => => setenv efi_selftest device tree
> >> => => setenv serial# Testing DT
> >> ## Error: Can't overwrite "serial#"
> >> ## Error inserting "serial#" variable, errno=1
> >> =>
> >>
> >> This worked without your patch.
> >>
> >> This patch does not solve any problem.
> >
> > This patch resolved the problems trying to use "env set -f" on platforms
> > where CONFIG_ENV_ACCESS_IGNORE_FORCE is unset and the variable is not
> > protected.  With:
> > commit 0f036bf4b87e6416f5c4d23865a62a62d9073c20
> > Author: Marek Vasut <marex@denx.de>
> > Date:   Tue Jul 7 20:51:33 2020 +0200
> >
> >     env: Warn on force access if ENV_ACCESS_IGNORE_FORCE set
> >
> > applied those platforms fail efi_selftest.  The answer I believe is that
> > on your platform serial# is protected so you do have to force
> > overwriting it in order to change it.  This is not the case of all
> > platforms with a serial# variable.
> 
> So no problem is solved except Marek's fancy warning.

It's not a "fancy warning".  It's an important bit of user feedback.  In
fact, the next question I keep coming back to is, how was, or is, this
working before?  Without Marek's patch, we silently return 0 and don't
change the variable.  With Marek's patch we tell the user we aren't
doing anything and return 0.  So are we actually changing serial# when
it's supposed to be unchangable?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200807/16824adb/attachment.sig>

      reply	other threads:[~2020-08-07 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 14:12 [PATCH] test: efi_selftest: Do not force serial# setting Tom Rini
2020-07-31 21:42 ` Tom Rini
2020-08-07 19:34   ` Heinrich Schuchardt
2020-08-07 19:50     ` Tom Rini
2020-08-07 19:56       ` Heinrich Schuchardt
2020-08-07 20:12         ` Tom Rini [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=20200807201243.GB20605@bill-the-cat \
    --to=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