All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Anders Olofsson <pingu@mazeda.se>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBI: Race between fastmap_write and wear_leveling_worker
Date: Thu, 25 Aug 2016 09:38:20 +0200	[thread overview]
Message-ID: <34d645bd-3c72-5d93-dd26-3215db9f92b9@nod.at> (raw)
In-Reply-To: <2022685b-c766-b37a-c6cb-5d662b260008@mazeda.se>

Anders,

On 25.08.2016 08:52, Anders Olofsson wrote:
> On 2016-08-24 17:04, Richard Weinberger wrote:
>> Anders,
>>
>> On Wed, Aug 24, 2016 at 1:37 PM, Anders Olofsson <pingu@mazeda.se> wrote:
>>> After enabling fastmap I sometimes get the following warning at boot:
>>>
>>
>> Hehe, you're lucky I've recently fixed an issue in this area, can you
>> please try:
>> http://lists.infradead.org/pipermail/linux-mtd/2016-August/068919.html
>>
>> I did these fixes on top of an rather old customer kernel and started
>> upstreaming
>> them.
>>
> 
> Tested it and from what I can tell it solves my problem as well. I've run a bunch of reboots and the wear leveling worker no longer runs while the fastmap is being updated.
> 
> Good work and thanks a lot for solving it so quickly.

How do you test? I wonder how you can trigger this so easily.
The said patch emerged while a customer did excessive Fastmap testing
and the race appeared only once. I found it while staring at the code.

But it is good to see that finally after years embedded Folks start
using Fastmap and non-obvious issues can get sorted out.

Thanks,
//richard

  reply	other threads:[~2016-08-25  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 11:37 UBI: Race between fastmap_write and wear_leveling_worker Anders Olofsson
2016-08-24 15:04 ` Richard Weinberger
2016-08-25  6:52   ` Anders Olofsson
2016-08-25  7:38     ` Richard Weinberger [this message]
2016-08-25  8:32       ` Anders Olofsson

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=34d645bd-3c72-5d93-dd26-3215db9f92b9@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pingu@mazeda.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.