mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 3/9] state: backend_raw: remove hard coded limit of two copies
Date: Tue, 26 May 2015 13:37:47 +0200	[thread overview]
Message-ID: <1432640273-3895-4-git-send-email-mkl@pengutronix.de> (raw)
In-Reply-To: <1432640273-3895-1-git-send-email-mkl@pengutronix.de>

Although there is the define RAW_BACKEND_COPIES, the state_backend_raw_save()
function silently assumes exactly two copies. This patch removes that assumtion
by looping over all copies, but saving the one we're read from at the end.

Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
 common/state.c | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/common/state.c b/common/state.c
index 82a21e912206..79e7f4cc6849 100644
--- a/common/state.c
+++ b/common/state.c
@@ -1167,7 +1167,7 @@ static int state_backend_raw_save(struct state_backend *backend,
 {
 	struct state_backend_raw *backend_raw = container_of(backend,
 			struct state_backend_raw, backend);
-	int ret = 0, size, fd;
+	int ret = 0, size, fd, i;
 	void *buf, *data;
 	struct backend_raw_header *header;
 	struct state_variable *sv;
@@ -1192,10 +1192,17 @@ static int state_backend_raw_save(struct state_backend *backend,
 	if (fd < 0)
 		goto out_free;
 
-	ret = backend_raw_write_one(backend_raw, state, fd,
-				    !backend_raw->num_copy_read, buf, size);
-	if (ret)
-		goto out_close;
+	/* save other slots first */
+	for (i = 0; i < RAW_BACKEND_COPIES; i++) {
+		if (i == backend_raw->num_copy_read)
+			continue;
+
+		ret = backend_raw_write_one(backend_raw, state, fd,
+					    i, buf, size);
+		if (ret)
+			goto out_close;
+
+	}
 
 	ret = backend_raw_write_one(backend_raw, state, fd,
 				    backend_raw->num_copy_read, buf, size);
-- 
2.1.4


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2015-05-26 11:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26 11:37 [PATCH 0/9] state: updates and cleanups to make code better sharable with linux Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 1/9] state: mtd_get_meminfo: open path readonly instead of readwrite Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 2/9] state: mtd_get_meminfo: make usage of mtd's meminfo compatible to linux Marc Kleine-Budde
2015-05-26 11:37 ` Marc Kleine-Budde [this message]
2015-05-26 11:37 ` [PATCH 4/9] state: backend_raw: rename struct state_backend_raw::step -> stride Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 5/9] state: backend_raw: properly align write and erase size Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 6/9] state: backend_raw: factor out state_backend_raw_file_get_size() into separate function Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 7/9] state: backend_raw: rename backend_raw_write_one() -> backend_raw_save_one() Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 8/9] state: backend_raw: add sanity check of data_len during load Marc Kleine-Budde
2015-05-26 11:37 ` [PATCH 9/9] state: backend_raw: update documentation of struct state_backend_raw members Marc Kleine-Budde
2015-05-26 12:33 ` [PATCH 0/9] state: updates and cleanups to make code better sharable with linux Sascha Hauer

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=1432640273-3895-4-git-send-email-mkl@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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