public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: David Mosberger-Tang <dmosberger@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] UBI: fix refill_wl_user_pool()
Date: Wed, 04 Sep 2013 18:01:36 +0200	[thread overview]
Message-ID: <52275960.20309@nod.at> (raw)
In-Reply-To: <CACwUX0PZ4RY6JDvOo7KS_rAFtUrUjPYmm2PG-PENMSkXq3CiSQ@mail.gmail.com>

David,

Am 04.09.2013 17:50, schrieb David Mosberger-Tang:
> Richard,
> 
> Is there more background on the bug this patch fixes?
> We are working on root-causing an issue where a UBIFS write fails with
> ENOSPC, even though there is no plausible reason that the filesystem
> should be out of space.  The ENOSPC errors persist across multiple
> reboots, only to disappear magically later on.  We haven't found a
> reliable way to reproduce this so far, so we're still tapping a bit in
> the dark.

The said patch fixes an issue if your Kernel was build with experimental Fastmap support.
If you have CONFIG_MTD_UBI_FASTMAP=n you are not affected.

Fastmap uses two pools of available PEBs. Every time a pool is filled with used PEBs
it writes out a new fastmap to the flash.
The bug in refill_wl_user_pool() was that the function did not try hard enough to get a free PEB
and failed too early with -ENOSPC.

Thanks,
//richard

>   --david
> 
> On Wed, Sep 4, 2013 at 2:20 AM, Richard Weinberger <richard@nod.at> wrote:
>> Am 26.08.2013 12:08, schrieb Richard Weinberger:
>>> If no free PEBs are available refill_wl_user_pool() must not
>>> return with -ENOSPC immediately.
>>> It has to block till produce_free_peb() produced a free PEB.
>>>
>>> Reported-and-Tested-by: Richard Genoud <richard.genoud@gmail.com>
>>> Signed-off-by: Richard Weinberger <richard@nod.at>
>>> ---
>>>  drivers/mtd/ubi/wl.c | 4 ----
>>>  1 file changed, 4 deletions(-)
>>>
>>> diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c
>>> index c95bfb1..02317c1 100644
>>> --- a/drivers/mtd/ubi/wl.c
>>> +++ b/drivers/mtd/ubi/wl.c
>>> @@ -599,10 +599,6 @@ static void refill_wl_user_pool(struct ubi_device *ubi)
>>>       return_unused_pool_pebs(ubi, pool);
>>>
>>>       for (pool->size = 0; pool->size < pool->max_size; pool->size++) {
>>> -             if (!ubi->free.rb_node ||
>>> -                (ubi->free_count - ubi->beb_rsvd_pebs < 1))
>>> -                     break;
>>> -
>>>               pool->pebs[pool->size] = __wl_get_peb(ubi);
>>>               if (pool->pebs[pool->size] < 0)
>>>                       break;
>>>
>>
>> Artem, please don't forget do apply this patch.
>>
>> Thanks,
>> //richard
>>
>> ______________________________________________________
>> Linux MTD discussion mailing list
>> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2013-09-04 16:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26 10:08 [PATCH] UBI: fix refill_wl_user_pool() Richard Weinberger
2013-09-04  8:20 ` Richard Weinberger
2013-09-04 15:50   ` David Mosberger-Tang
2013-09-04 16:01     ` Richard Weinberger [this message]
2013-09-04 16:03       ` David Mosberger-Tang
2013-09-05  6:09         ` Richard Weinberger
2013-09-05 17:16           ` David Mosberger-Tang
2013-09-20 16:09   ` richard -rw- 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=52275960.20309@nod.at \
    --to=richard@nod.at \
    --cc=dmosberger@gmail.com \
    --cc=linux-mtd@lists.infradead.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