From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: linux equivalent of u-boot's "nand scrub" (erasing blocks even when OOB says "bad")
Date: Sun, 12 Sep 2010 10:54:03 +0300 [thread overview]
Message-ID: <1284278043.1783.10.camel@brekeke> (raw)
In-Reply-To: <AANLkTinHKU1BfmtZyEKFwUVFJz9YoPr93D7tP6jqXeJE@mail.gmail.com>
On Sun, 2010-09-12 at 00:03 -0400, Mike Frysinger wrote:
> On Sat, Sep 11, 2010 at 02:32, Artem Bityutskiy wrote:
> > On Fri, 2010-09-10 at 19:53 -0400, Mike Frysinger wrote:
> >> the logical thing in my mind would be to extend the userspace mtd abi
> >> to allow a "do the erase even if people think it's bad" option.
> >> perhaps MEMSCRUB ?
> >
> > If you do this, please do not use this name. In UBI we already use term
> > 'scrubbing' for the process when we move contents of eraseblock because
> > we have bit-flips.
>
> that doesnt sound like scrubbing at all, but too late now i guess to fix
Not sure, I'm not native English speaker, and actually that was not me
who called the process this way.
> > It will be confusing if the same word is used in MTD for "unmarking"
> > eraseblocks. How about: 'force erase' or 'bad erase' ?
>
> that makes it sound like an option to the existing MEMERASE operation.
> so i guess what if we just do that -- extend the erase_info_user
> structure to contain a flags field and add a MEMERASE2 that works with
> the larger structure ? for now we'd only have one option (FORCE), but
> it makes it easy to extend in the future.
Ohh, this was so stupid of me to not ask people to add extra fields to
'struct erase_info_user64' which was introduced relatively recently... I
always add extra fields to ioctl data structures...
But yeah, what you say sounds ok to me.
--
Best Regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2010-09-12 7:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 23:53 linux equivalent of u-boot's "nand scrub" (erasing blocks even when OOB says "bad") Mike Frysinger
2010-09-11 6:32 ` Artem Bityutskiy
2010-09-12 4:03 ` Mike Frysinger
2010-09-12 7:54 ` Artem Bityutskiy [this message]
2010-09-22 7:43 ` Mike Frysinger
2010-09-23 12:28 ` Artem Bityutskiy
2010-09-23 19:55 ` Mike Frysinger
2010-09-24 8:47 ` Artem Bityutskiy
2010-09-13 5:54 ` linux equivalent of u-boot's "nand scrub" (erasing blocks even whenOOB " Jon Povey
2010-09-13 6:25 ` Artem Bityutskiy
2010-09-14 1:16 ` Mike Frysinger
2010-09-14 1:53 ` Jon Povey
2010-09-14 1:59 ` Mike Frysinger
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=1284278043.1783.10.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.