From: Artem Bityutskiy <dedekind@infradead.org>
To: Brijesh Singh <brij.singh@samsung.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [UBI] Volume table update fix
Date: Mon, 22 Jun 2009 10:29:56 +0300 [thread overview]
Message-ID: <1245655796.9487.29.camel@localhost.localdomain> (raw)
In-Reply-To: <6b5362aa0906190401l51bcf28bg44b9a7a9f49aa773@mail.gmail.com>
Hi,
thanks for the patch. Below are my minor/stylistic notes.
> diff --git a/drivers/mtd/ubi/vtbl.c b/drivers/mtd/ubi/vtbl.c
> index 1afc61e..c776037 100644
> --- a/drivers/mtd/ubi/vtbl.c
> +++ b/drivers/mtd/ubi/vtbl.c
> @@ -84,7 +84,7 @@ static struct ubi_vtbl_record empty_vtbl_record;
> int ubi_change_vtbl_record(struct ubi_device *ubi, int idx,
> struct ubi_vtbl_record *vtbl_rec)
> {
> - int i, err;
> + int copy, err, err1;
> uint32_t crc;
> struct ubi_volume *layout_vol;
>
> @@ -99,19 +99,41 @@ int ubi_change_vtbl_record(struct ubi_device *ubi, int idx,
> }
>
> memcpy(&ubi->vtbl[idx], vtbl_rec, sizeof(struct ubi_vtbl_record));
> - for (i = 0; i < UBI_LAYOUT_VOLUME_EBS; i++) {
> - err = ubi_eba_unmap_leb(ubi, layout_vol, i);
> + for (copy = 0; copy < UBI_LAYOUT_VOLUME_EBS; copy++) {
> + err = ubi_eba_unmap_leb(ubi, layout_vol, copy);
> if (err)
> - return err;
> + goto out_error;
>
> - err = ubi_eba_write_leb(ubi, layout_vol, i, ubi->vtbl, 0,
> + err = ubi_eba_write_leb(ubi, layout_vol, copy, ubi->vtbl, 0,
> ubi->vtbl_size, UBI_LONGTERM);
> if (err)
> - return err;
> + goto out_error;
> }
>
> paranoid_vtbl_check(ubi);
> return 0;
> +
> +out_error:
> + /* If first copy was written,volume creation is successful.
> + * But switch to read only mode as we have only one copy.
> + * If first copy itself was not written, older version is in copy 2.
> + * Unmap first copy and call wl_flush.
> + * Volume creating is unsuccessful.
> + */
Please, clean-up the comment. Split lines nicer - you have 79 characters
per line, use the same starting '/*' as other UBI comments do. Just
glance at the other UBI comments. BTW, the commit message has somewhat
unclean line splitting as well.
> + ubi_err("Error writing volume table copy #%d", copy+1);
UBI prints should not start with capital letters, because the printing
macros add prefixes. Take a look at other UBI prints.
> + err1 = ubi_eba_unmap_leb(ubi, layout_vol, copy);
> + if (!err1) {
> + ubi_wl_flush(ubi);
> + /* Don't bother about error in flush
> + * We are going read only any ways
> + */
Please. clean up this comment a little. You might as well just kill it.
> + }
> + ubi_ro_mode(ubi);
> + ubi_msg("Try detaching and attaching UBI again");
Please, remove this message. The kernel messages should not be used for
suggestions like this. They are not FAQ.
> + if (copy > 0)
> + return 0;
> + else
> + return err;
This is a tricky place, IMO, and deserves a comment. Could we have
something like:
/*
* If the first volume table copy has been changed then overall the
* operation has succeeded, because the change would be there if we now
* re-attached the UBI device. Thus, return success in this case.
*/
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-06-22 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 11:01 [PATCH] [UBI] Volume table update fix Brijesh Singh
2009-06-22 7:29 ` Artem Bityutskiy [this message]
2009-06-22 7:34 ` Artem Bityutskiy
2009-06-22 11:14 ` Brijesh Singh
2009-06-22 13:11 ` 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=1245655796.9487.29.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=brij.singh@samsung.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