From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Woodhouse <dwmw2@infradead.org>, Greg KH <greg@kroah.com>,
Steve deRosier <derosier@gmail.com>,
Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
dedekind1@gmail.com, tharvey@gateworks.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
cyrille.pitchen@wedev4u.fr, computersforpeace@gmail.com
Subject: Re: [PATCH] ubi: Reject MLC NAND
Date: Wed, 7 Mar 2018 23:30:57 +0100 [thread overview]
Message-ID: <20180307233057.54bd35c3@bbrezillon> (raw)
In-Reply-To: <20180307221733.GE10438@amd>
Hi Pavel,
On Wed, 7 Mar 2018 23:17:33 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> On Wed 2018-03-07 22:11:13, David Woodhouse wrote:
> >
> >
> > On Wed, 2018-03-07 at 14:08 -0800, Steve deRosier wrote:
> > >
> > > To clarify one thing: the reason for this is MLC has actually never
> > > been supported, nor worked properly. The fact that it kinda worked was
> > > incidental and the cause of major problems for people due to that not
> > > being clear. This patch only makes it explicit and avoids people
> > > mistakenly trying to use UBIFS on MLC flash and risking their data and
> > > products. To me, that's what's important.
> > >
> > > This is an important patch, even if all it does is keep people from
> > > loosing data. It also changes the conversation from "I have a
> > > corrupted UBIFS device, BTW it's on MLC..." to "What can we do to get
> > > UBIFS to work on MLC".
>
> Well, for -stable I'd suggest printk(KERN_ALERT ...) but keep the
> system running.
>
> > This is a bug fix.
> >
> > UBI on MLC never worked. It was a bug that we ever permitted it. This
> > is now fixed.
>
> Yeah, well, so lets say I have a working hardware (maybe using
> read-only UBI on MLC), update to next stable kernel, and now kernel
> refuses to see the partition.
Read-only does not save you from the read-disturb issue, and you even
have to take care of programming the full erase-block on some MLC
NANDs, which AFAIR is not done when updating a static volume.
I have one simple question: did you ever play with MLC NANDs or are you
just trolling? If you had, like Richard and I did when working on MLC
support, I'm pretty sure you wouldn't play this "don't backport to
stable" card.
Now, if you volunteer to add reliable MLC support, I can send you a
few boards to play with. I even have a "working but not so tested PoC"
here [1] if you want to finish the job, but please don't do the mistake
of thinking the fix is that simple.
>
> I'll certainly not consider this patch a bug fix.
And apparently a lot of people disagree with you on this point, and I
guess all of them had problems with MLC NANDs.
>
> Removing support for hardware that "only works by mistake" may be good
> idea, but maybe it is slightly too surprising for a -stable.
I wouldn't say "work by mistake" but "seems to work at first but in the
end breaks", so definitely a candidate for -stable IMO.
Regards,
Boris
[1]https://github.com/bbrezillon/linux/tree/nand/mlc
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-07 22:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 10:45 [PATCH] ubi: Reject MLC NAND Richard Weinberger
2018-03-04 19:46 ` Boris Brezillon
2018-03-06 23:18 ` Pavel Machek
2018-03-07 1:57 ` David Oberhollenzer
2018-03-07 8:01 ` Richard Weinberger
2018-03-07 15:24 ` Artem Bityutskiy
2018-03-07 21:43 ` Pavel Machek
2018-03-07 22:08 ` Steve deRosier
2018-03-07 22:11 ` David Woodhouse
2018-03-07 22:17 ` Pavel Machek
2018-03-07 22:30 ` Boris Brezillon [this message]
2018-03-07 23:27 ` Willy Tarreau
2018-03-07 22:40 ` Boris Brezillon
2018-03-08 13:42 ` Linus Walleij
2018-03-08 14:43 ` Richard Weinberger
2018-03-08 15:01 ` Artem Bityutskiy
2018-03-08 15:28 ` Richard Weinberger
2018-03-08 15:34 ` 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=20180307233057.54bd35c3@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dedekind1@gmail.com \
--cc=derosier@gmail.com \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=tharvey@gateworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox