From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: Martinbayern@outlook.com, stable@vger.kernel.org
Subject: Re: [PATCH] ubi: fastmap: Correctly handle interrupted erasures in EBA
Date: Thu, 5 Jul 2018 20:10:02 +0200 [thread overview]
Message-ID: <20180705181002.GA4575@kroah.com> (raw)
In-Reply-To: <20180701182530.24735-1-richard@nod.at>
On Sun, Jul 01, 2018 at 08:25:30PM +0200, Richard Weinberger wrote:
> Fastmap cannot track the LEB unmap operation, therefore it can
> happen that after an interrupted erasure the mapping still looks
> good from Fastmap's point of view, while reading from the PEB will
> cause an ECC error and confuses the upper layer.
>
> Instead of teaching users of UBI how to deal with that, we read back
> the VID header and check for errors. If the PEB is empty or shows ECC
> errors we fixup the mapping and schedule the PEB for erasure.
>
> Fixes: dbb7d2a88d2a ("UBI: Add fastmap core")
> Cc: <stable@vger.kernel.org>
> Reported-by: martin bayern <Martinbayern@outlook.com>
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> Hi Greg,
>
> This is the backport of 781932375ffc ("ubi: fastmap: Correctly handle interrupted erasures in EBA")
> for 3.18-stable.
Now applied, thanks.
greg k-h
next prev parent reply other threads:[~2018-07-05 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 13:25 FAILED: patch "[PATCH] ubi: fastmap: Correctly handle interrupted erasures in EBA" failed to apply to 3.18-stable tree gregkh
2018-07-01 18:25 ` [PATCH] ubi: fastmap: Correctly handle interrupted erasures in EBA Richard Weinberger
2018-07-05 18:10 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-01 13:25 FAILED: patch "[PATCH] ubi: fastmap: Correctly handle interrupted erasures in EBA" failed to apply to 4.4-stable tree gregkh
2018-07-01 18:24 ` [PATCH] ubi: fastmap: Correctly handle interrupted erasures in EBA Richard Weinberger
2018-07-05 18:10 ` Greg KH
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=20180705181002.GA4575@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Martinbayern@outlook.com \
--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;
as well as URLs for NNTP newsgroup(s).