public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	cyrille.pitchen@wedev4u.fr, marek.vasut@gmail.com,
	boris.brezillon@free-electrons.com, computersforpeace@gmail.com,
	dwmw2@infradead.org, dedekind1@gmail.com, tharvey@gateworks.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] ubi: Reject MLC NAND
Date: Wed, 7 Mar 2018 23:40:51 +0100	[thread overview]
Message-ID: <20180307234051.479d9eed@bbrezillon> (raw)
In-Reply-To: <20180307214342.GA9852@amd>

On Wed, 7 Mar 2018 22:43:42 +0100
Pavel Machek <pavel@ucw.cz> wrote:

> On Wed 2018-03-07 09:01:16, Richard Weinberger wrote:
> > Pavel,
> > 
> > Am Mittwoch, 7. März 2018, 00:18:05 CET schrieb Pavel Machek:  
> > > On Sat 2018-03-03 11:45:54, Richard Weinberger wrote:  
> > > > While UBI and UBIFS seem to work at first sight with MLC NAND, you will
> > > > most likely lose all your data upon a power-cut or due to read/write
> > > > disturb.
> > > > In order to protect users from bad surprises, refuse to attach to MLC
> > > > NAND.
> > > > 
> > > > Cc: stable@vger.kernel.org  
> > > 
> > > That sounds like _really_ bad idea for stable. All it does is it
> > > removes support for hardware that somehow works.  
> > 
> > MLC is not supported and does not work. Full stop.
> > If someone manages to get it somehow work, either with hardware or software 
> > hacks they are on their own.
> > Having it in stable is the only chance we have to get it into vendor
> > kernels.  
> 
> Can you show how it meets the stable kernel criteria? They are
> documented in tree. This should not be in stable.
> 
> And I'd like to see changelog improved. Real reason MLC is not
> supported is upper/lower page parts on MLC. And real fix to work with
> bigger pages in UBI.

Come on! Don't you think this would have been fixed already if it was
that easy?! Have you looked at an MLC datasheet to see how paired pages
are combined? If you had you would now that paired pages are almost all
the time not contiguous, thus preventing the trick you're suggesting
here. Please document yourself before doing such presumptuous
statements (you can have a look at these slides if you want some details
about why this is not so simple [1]).

I'm definitely not saying supporting MLC NANDs in Linux is impossible,
and if you're interested in working on this topic I'd be happy to help.
But please don't block this patch without understanding what supporting
MLC NANDs implies.

[1]https://events.static.linuxfound.org/sites/events/files/slides/ubi-mlc.pdf

-- 
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-03-07 22:41 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
2018-03-07 23:27               ` Willy Tarreau
2018-03-07 22:40       ` Boris Brezillon [this message]
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=20180307234051.479d9eed@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=dwmw2@infradead.org \
    --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