From: Huang Shijie <shijie8@gmail.com>
To: Elie De Brauwer <eliedebrauwer@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v6] mtd: gpmi: Deal with bitflips in erased regions regions
Date: Fri, 3 Jan 2014 23:16:49 +0800 [thread overview]
Message-ID: <20140103151647.GA1766@gmail.com> (raw)
In-Reply-To: <CAGWqfiiQ0V0FGGV0UiTqw9wpqUtb2hFh2mj+WhMx8_zmct1OyA@mail.gmail.com>
On Fri, Jan 03, 2014 at 11:34:54AM +0100, Elie De Brauwer wrote:
> >
> > I confirmed with the hardware guy just now.
> > the hardware guy ate his word!
> >
> > If we do not apply this patch, does it mean the UBIFS can not work?
> >
> >
>
> Thanks for doublechecking ! I'll provide a new version of this patch
> in the weekend.
>
> If this patch does not get applied you will get bugreports related to
> "corrupt empty space"
> issues when using UBIFS, for the simple reason that ubifs only claims
> to be tolerant to
> corruption due to powercuts, and ubifs relies on the mtd layer that
> bitflips are detected
> and corrected. In my situation I have already seen two distinct units
> (on a 20 unit population
> over a timespan of about two months) refuse to boot because of this
> issue, which were
> both solved by this patch. So ubifs might seem to work, but people
> using it will likely bump
> into nasty field issues.
I will discuss with our manager next week, and i hope the hardware guy
can fix it in the future.
thanks
Huang Shijie
prev parent reply other threads:[~2014-01-03 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 19:07 [PATCH v6] gpmi-nand bitflips in erased regions Elie De Brauwer
2013-12-18 19:07 ` [PATCH v6] mtd: gpmi: Deal with bitflips in erased regions regions Elie De Brauwer
2013-12-19 5:10 ` Huang Shijie
2014-01-03 9:43 ` Elie De Brauwer
2014-01-03 9:44 ` Huang Shijie
2014-01-03 10:34 ` Elie De Brauwer
2014-01-03 15:16 ` Huang Shijie [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=20140103151647.GA1766@gmail.com \
--to=shijie8@gmail.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eliedebrauwer@gmail.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 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.