U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Faustini <nicholas.faustini@azcomtech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save()
Date: Tue, 10 Jul 2018 14:57:56 +0200	[thread overview]
Message-ID: <1531227476-21591-1-git-send-email-nicholas.faustini@azcomtech.com> (raw)

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.

The env_save() function should not loop through the environment
location list but it should use the previously discovered
environment driver once.

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

             reply	other threads:[~2018-07-10 12:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 12:57 Nicholas Faustini [this message]
2018-07-10 20:49 ` [U-Boot] [RFC PATCH] u-boot: remove driver lookup loop from env_save() 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

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=1531227476-21591-1-git-send-email-nicholas.faustini@azcomtech.com \
    --to=nicholas.faustini@azcomtech.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