From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:46908 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753450AbeGESKG (ORCPT
        <rfc822;stable@vger.kernel.org>); Thu, 5 Jul 2018 14:10:06 -0400
Date: Thu, 5 Jul 2018 20:10:02 +0200
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
Message-ID: <20180705181002.GA4575@kroah.com>
References: <153045152812710@kroah.com>
 <20180701182530.24735-1-richard@nod.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180701182530.24735-1-richard@nod.at>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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