public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: jean-philippe francois <jp.francois@cynove.com>
Cc: richard@nod.at,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	stable@vger.kernel.org
Subject: Re: Ubi patch proposition for 3.10.y
Date: Mon, 08 Sep 2014 12:58:38 +0300	[thread overview]
Message-ID: <1410170318.10764.119.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAGGh5h0KjexqaoEt8vvVXAEqCr625675XG4d71KdEuhrQVPr3w@mail.gmail.com>

On Fri, 2014-08-29 at 14:26 +0200, jean-philippe francois wrote:
> Hi,
> 
> I think commit 4b3e0a25... [1] (UBI: Call scan_all() with correct
> offset in error case) should be added to 3.10.y stable branch.

This is the "fastmap" fix, and fastmap is called experimental. We do not
have enough confidence it is production ready. Specifically, I'd like to
hear someone doing extensive power-cut testing with this feature. The
power-cut tolerance is one of the "selling features" of UBI/UBIFS, after
all.

Therefore I never added fastmap fixes to the stable queue.

But if someone is willing to put all the fastmap fixes together, add the
"stable tags" with the right kernel version "markings", and test for few
older kernels, then I will recommend them to be included to the stable.
Although I am not sure the stable maintainers would like accept them.

But I do not recommend adding this single patch to the stable queue.

But better, if people started paying more attention to "fastmap", we may
agree that from now on we are careful about the sending the fixes to the
stable queue.

Thanks!

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2014-09-08  9:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 12:26 Ubi patch proposition for 3.10.y jean-philippe francois
2014-09-01 21:51 ` Richard Weinberger
2014-09-01 22:02   ` Greg KH
2014-09-03 22:08     ` Richard Weinberger
2014-09-08  9:47       ` Artem Bityutskiy
2014-09-08  9:51         ` Richard Weinberger
2014-09-08  9:58 ` Artem Bityutskiy [this message]
2014-09-08 10:04   ` Willy Tarreau
2014-09-08 10:13     ` Richard Genoud
2014-09-08 10:13     ` Artem Bityutskiy
2014-09-08 10:53       ` Willy Tarreau
2014-09-08 11:03       ` jean-philippe francois
2014-09-08 10:16   ` Richard Weinberger

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=1410170318.10764.119.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=jp.francois@cynove.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.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