From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: "J. Scott Merritt" <merrij3@rpi.edu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubinize corrections
Date: Mon, 03 Nov 2008 10:41:58 +0200 [thread overview]
Message-ID: <490EB956.5050700@nokia.com> (raw)
In-Reply-To: <20081102142315.453628de.merrij3@rpi.edu>
J. Scott Merritt wrote:
> Dear list,
>
> I believe that I have stumbled upon two problems with the latest version
> of ubinize.c in mtd-utils - one serious, and one not so serious.
>
> - First, the easy one: At line 457, I believe that we should be printing
> args.subpage_size rather than ui.min_io_size.
>
> - More seriously, I believe that the "flags" field in the ubigen_vol_info
> structures is not being properly initialized. Line 494 allocates memory
> for these structures with malloc, so they are not cleared to zero. The
> read_section function updates the flag field if the AUTO-RESIZE flag is
> specified, but does not otherwise initialize or clear it.
>
> I reckon the latter problem could be repaired either with calloc, or by
> modifying read_section to more directly set/clear the flag.
>
> Thanks, Scott.
I agree. Here's the patch:
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
Date: Mon, 3 Nov 2008 10:36:32 +0200
Subject: [PATCH] ubinize: correct subpage_size print and initialise vol_info to zero
Reported-by: "J. Scott Merritt" <merrij3@rpi.edu>
Signed-off-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
---
ubi-utils/new-utils/src/ubinize.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/ubi-utils/new-utils/src/ubinize.c b/ubi-utils/new-utils/src/ubinize.c
index ebd5aa0..4f3e8a1 100644
--- a/ubi-utils/new-utils/src/ubinize.c
+++ b/ubi-utils/new-utils/src/ubinize.c
@@ -454,7 +454,7 @@ int main(int argc, char * const argv[])
verbose(args.verbose, "LEB size: %d", ui.leb_size);
verbose(args.verbose, "PEB size: %d", ui.peb_size);
verbose(args.verbose, "min. I/O size: %d", ui.min_io_size);
- verbose(args.verbose, "sub-page size: %d", ui.min_io_size);
+ verbose(args.verbose, "sub-page size: %d", args.subpage_size);
verbose(args.verbose, "VID offset: %d", ui.vid_hdr_offs);
verbose(args.verbose, "data offset: %d", ui.data_offs);
@@ -491,7 +491,7 @@ int main(int argc, char * const argv[])
goto out_dict;
}
- vi = malloc(sizeof(struct ubigen_vol_info) * sects);
+ vi = calloc(sizeof(struct ubigen_vol_info), sects);
if (!vi) {
errmsg("cannot allocate memory");
goto out_dict;
next prev parent reply other threads:[~2008-11-03 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 19:23 ubinize corrections J. Scott Merritt
2008-11-03 8:41 ` Adrian Hunter [this message]
2008-11-03 16:49 ` J. Scott Merritt
2008-11-06 7:13 ` Artem Bityutskiy
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=490EB956.5050700@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=merrij3@rpi.edu \
/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