From: Artem Bityutskiy <dedekind1@gmail.com>
To: b35362@freescale.com
Cc: linuxppc-dev@linux.freescale.net, dwmw2@infradead.org,
linux-mtd@lists.infradead.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] mtd-utils: fix corrupt cleanmarker with flash_erase -j command
Date: Tue, 16 Aug 2011 18:06:35 +0300 [thread overview]
Message-ID: <1313507201.2679.2.camel@sauron> (raw)
In-Reply-To: <1312350638-25566-1-git-send-email-b35362@freescale.com>
On Wed, 2011-08-03 at 13:50 +0800, b35362@freescale.com wrote:
> From: Liu Shuo <b35362@freescale.com>
>
> Flash_erase -j should fill discrete freeoob areas with required bytes
> of JFFS2 cleanmarker in jffs2_check_nand_cleanmarker(). Not just fill
> the first freeoob area.
>
> Signed-off-by: Liu Shuo <b35362@freescale.com>
> Signed-off-by: Li Yang <leoli@freescale.com>
...
> /*
> * Process user arguments
> @@ -197,15 +198,40 @@ int main(int argc, char *argv[])
> if (ioctl(fd, MEMGETOOBSEL, &oobinfo) != 0)
> return sys_errmsg("%s: unable to get NAND oobinfo", mtd_device);
>
> + cleanmarker.totlen = cpu_to_je32(8);
> /* Check for autoplacement */
> if (oobinfo.useecc == MTD_NANDECC_AUTOPLACE) {
> + struct nand_ecclayout_user ecclayout;
> /* Get the position of the free bytes */
> - if (!oobinfo.oobfree[0][1])
> + if (ioctl(fd, ECCGETLAYOUT, &ecclayout) != 0)
> + return sys_errmsg("%s: unable to get NAND ecclayout", mtd_device);
> +
Hmm, shouldn't we instead make MTD_OOB_AUTO be available for userspace
via an ioctl instead and make flash_eraseall use it instead?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-08-16 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 5:50 [PATCH] mtd-utils: fix corrupt cleanmarker with flash_erase -j command b35362
2011-08-16 15:06 ` Artem Bityutskiy [this message]
2011-08-16 19:42 ` Brian Norris
2011-08-17 7:35 ` LiuShuo
2011-08-17 7:39 ` Artem Bityutskiy
2011-08-18 1:20 ` Brian Norris
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=1313507201.2679.2.camel@sauron \
--to=dedekind1@gmail.com \
--cc=b35362@freescale.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@linux.freescale.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).