From: Artem Bityutskiy <dedekind@infradead.org>
To: Holger Brunck <holger.brunck@keymile.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] UBI: fix bug in image sequence number handling
Date: Tue, 14 Jul 2009 08:43:20 +0300 [thread overview]
Message-ID: <1247550200.8109.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1247496477.3590.40.camel@pc005093.de.keymile.net>
On Mon, 2009-07-13 at 16:47 +0200, Holger Brunck wrote:
> Hi all,
> I have seen a bug on the current 2.6.28 backport for UBI. But the same
> bug seems to be present in the current ubi-2.6.git.
>
>
> This patch fixes a bug in the image seq. number handling in the
> scanning level. The assignment of the image_seq was incorrect.
>
> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
> ---
> drivers/mtd/ubi/scan.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mtd/ubi/scan.c b/drivers/mtd/ubi/scan.c
> index 065c4ba..e337b0b 100644
> --- a/drivers/mtd/ubi/scan.c
> +++ b/drivers/mtd/ubi/scan.c
> @@ -781,7 +781,7 @@ static int process_eb(struct ubi_device *ubi, struct
> ubi_scan_info *si,
> return -EINVAL;
> }
>
> - image_seq = be32_to_cpu(ech->ec);
> + image_seq = be32_to_cpu(ech->image_seq);
> if (!si->image_seq_set) {
> ubi->image_seq = image_seq;
> si->image_seq_set = 1;
Yes, this is me who did this in the
"UBI: nicify image sequence number handling" commit. Sorry, really
shame bug. Where is my brown paper-bag? I've pushed your patch to
all trees.
BTW, the patch was line-wrapped.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-07-14 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 14:47 [PATCH] UBI: fix bug in image sequence number handling Holger Brunck
2009-07-14 5:43 ` Artem Bityutskiy [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=1247550200.8109.9.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=holger.brunck@keymile.com \
--cc=linux-mtd@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