stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] ubi: Make volume resize power cut aware
Date: Thu, 23 Jun 2016 22:46:28 +0200	[thread overview]
Message-ID: <20160623224628.0495c565@bbrezillon> (raw)
In-Reply-To: <1466703038-13044-1-git-send-email-richard@nod.at>

On Thu, 23 Jun 2016 19:30:38 +0200
Richard Weinberger <richard@nod.at> wrote:

> When the volume resize operation shrinks a volume,
> LEBs will be unmapped. Since unmapping will not erase these
> LEBs immediately we have to wait for that operation to finish.
> Otherwise in case of a power cut right after writing the new
> volume table the UBI attach process can find more LEBs than the
> volume table knows. This will render the UBI image unattachable.
> 
> Fix this issue by waiting for erase to complete and write the new volume table afterward.
> 
> Cc: <stable@vger.kernel.org>
> Reported-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Signed-off-by: Richard Weinberger <richard@nod.at>

I hope this change won't uncover another bug in case some of the
UBI logic rely on the 'write vtbl record, then unmap unused LEBs'
sequence. But AFAICT it seems safe.

You should probably wait for other reviews before taking the patch
though.

Reviewed-by: Boris Brezillon <boris.brezillon@free-electrons.com>

> ---
>  drivers/mtd/ubi/vmt.c | 25 ++++++++++++++++++-------
>  1 file changed, 18 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/mtd/ubi/vmt.c b/drivers/mtd/ubi/vmt.c
> index 10059df..0138f52 100644
> --- a/drivers/mtd/ubi/vmt.c
> +++ b/drivers/mtd/ubi/vmt.c
> @@ -488,13 +488,6 @@ int ubi_resize_volume(struct ubi_volume_desc *desc, int reserved_pebs)
>  		spin_unlock(&ubi->volumes_lock);
>  	}
>  
> -	/* Change volume table record */
> -	vtbl_rec = ubi->vtbl[vol_id];
> -	vtbl_rec.reserved_pebs = cpu_to_be32(reserved_pebs);
> -	err = ubi_change_vtbl_record(ubi, vol_id, &vtbl_rec);
> -	if (err)
> -		goto out_acc;
> -
>  	if (pebs < 0) {
>  		for (i = 0; i < -pebs; i++) {
>  			err = ubi_eba_unmap_leb(ubi, vol, reserved_pebs + i);
> @@ -512,6 +505,24 @@ int ubi_resize_volume(struct ubi_volume_desc *desc, int reserved_pebs)
>  		spin_unlock(&ubi->volumes_lock);
>  	}
>  
> +	/*
> +	 * When we shrink a volume we have to flush all pending (erase) work.
> +	 * Otherwise it can happen that upon next attach UBI finds a LEB with
> +	 * lnum > highest_lnum and refuses to attach.
> +	 */
> +	if (pebs < 0) {
> +		err = ubi_wl_flush(ubi, vol_id, UBI_ALL);
> +		if (err)
> +			goto out_acc;
> +	}
> +
> +	/* Change volume table record */
> +	vtbl_rec = ubi->vtbl[vol_id];
> +	vtbl_rec.reserved_pebs = cpu_to_be32(reserved_pebs);
> +	err = ubi_change_vtbl_record(ubi, vol_id, &vtbl_rec);
> +	if (err)
> +		goto out_acc;
> +
>  	vol->reserved_pebs = reserved_pebs;
>  	if (vol->vol_type == UBI_DYNAMIC_VOLUME) {
>  		vol->used_ebs = reserved_pebs;


  reply	other threads:[~2016-06-23 20:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 17:30 [PATCH] ubi: Make volume resize power cut aware Richard Weinberger
2016-06-23 20:46 ` Boris Brezillon [this message]
2016-06-23 21:17   ` Richard Weinberger
2016-06-24 18:05 ` Ezequiel Garcia
2016-06-24 19:15   ` 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=20160623224628.0495c565@bbrezillon \
    --to=boris.brezillon@free-electrons.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;
as well as URLs for NNTP newsgroup(s).