All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save()
Date: Wed, 11 Jul 2018 09:37:58 +0200	[thread overview]
Message-ID: <20180711093758.6d5162f8@jawa> (raw)
In-Reply-To: <CAPnjgZ1oH_h6LjMrrqnJuSLDwozDe+v5BBnCqOgyeXPHScHKVA@mail.gmail.com>

Hi Simon,

> Hi Nicholas,
> 
> On 10 July 2018 at 06:57, Nicholas Faustini
> <nicholas.faustini@azcomtech.com> wrote:
> > When called with ENVOP_SAVE, env_get_location() only returns the
> > gd->env_load_location variable without actually checking for
> > the environment location and priority. This allows saving the
> > environment into the same location that has been previously loaded.
> >
> > This behaviour causes env_save() to fall into an infinite loop when
> > the low-level drv->save() call fails.  
> 
> Why is this? Should it not stop eventually? 

I can confirm that there is a problem as described here - when you fail
to write to eMMC device (like e.g. 2, not 0), then we loop forever.

I do see such situation with Odroid XU3 when switching to BLK.

> Do we need a limit on
> prio?
> 
> >
> > The env_save() function should not loop through the environment
> > location list but it should use the previously discovered
> > environment driver once.  
> 
> What is that? It should be possible to write the env to multiple
> places. Also what is the previously discovered environment?
> 
> >
> > Signed-off-by: Nicholas Faustini <nicholas.faustini@azcomtech.com>
> > ---
> >
> >  env/env.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/env/env.c b/env/env.c
> > index 5c0842a..897d197 100644
> > --- a/env/env.c
> > +++ b/env/env.c
> > @@ -211,16 +211,16 @@ int env_load(void)
> >  int env_save(void)
> >  {
> >         struct env_driver *drv;
> > -       int prio;
> >
> > -       for (prio = 0; (drv = env_driver_lookup(ENVOP_SAVE, prio));
> > prio++) {
> > +       drv = env_driver_lookup(ENVOP_SAVE, 0);
> > +       if (drv) {
> >                 int ret;
> >
> >                 if (!drv->save)
> > -                       continue;
> > +                       return -ENODEV;
> >
> >                 if (!env_has_inited(drv->location))
> > -                       continue;
> > +                       return -ENODEV;
> >
> >                 printf("Saving Environment to %s... ", drv->name);
> >                 ret = drv->save();
> > --
> > 2.7.4
> >  
> 
> Regards,
> Simon




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180711/028ac2f8/attachment.sig>

      parent reply	other threads:[~2018-07-11  7:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 12:57 [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save() Nicholas Faustini
2018-07-10 20:49 ` Simon Glass
2018-07-11  4:57   ` Simon Goldschmidt
2018-07-11  5:09   ` Simon Goldschmidt
2018-07-11  8:33     ` Nicholas
2018-07-11  9:48       ` Maxime Ripard
2018-07-11 10:01         ` Simon Goldschmidt
2018-07-11 10:44           ` Nicholas
2018-07-11 13:50             ` Maxime Ripard
2018-07-12  7:02               ` Simon Goldschmidt
2018-07-12  7:20                 ` Maxime Ripard
2018-07-17  4:48                   ` Simon Goldschmidt
2018-07-11 10:49         ` Wolfgang Denk
2018-07-11 13:47           ` Maxime Ripard
2018-07-11 13:54             ` Wolfgang Denk
2018-07-11  7:37   ` Lukasz Majewski [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=20180711093758.6d5162f8@jawa \
    --to=lukma@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.