Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1224918

Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report timeouts

Path csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From Alex Smith <alex@alex-smith.me.uk>
Newsgroups linux.kernel
Subject Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report timeouts
Date Tue, 15 Sep 2015 11:40:04 +0200
Message-ID <q8USw-QT-73@gated-at.bofh.it> (permalink)
References <q6neh-8nx-3@gated-at.bofh.it> <q6nei-8nx-11@gated-at.bofh.it> <q6XhM-1ek-5@gated-at.bofh.it>
X-Original-To Brian Norris <computersforpeace@gmail.com>, Niklas Cassel <niklass@axis.com>
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=XuKXjRwSz0LL10BUwlgAl4vi6jvoTFc70OckuFat8j0=; b=LqfUzfCUpM+yqK6XX5FeTBVoDMvZgPEDNla6YgNgCbdhyoGFnfMAvSREL8DR6XRRPy CFV4YLLKNqUIBB095Y1AyzcFBw87S5N0N4VO3T5L9XzArxPgaIJaCgs1kGrrtbbGWEot Km4qSAAWvTq97cMy3WBMwhswctuMW3C/FFfVo6ak00cBExLbwz2nnIwYtrmLadPEMd6G 9q4Emf38FU5dE7UT9oKqt68hGrjvJQ/wq+w5OeE8Mr58ndSCMO3ov7ZtC0ILRwWoIJJu 8cPgBpEcFZmq1yIi/HoC+Zqr1WJOAAoOcnr42QKKYB9UWdYhQypv/inhd9xfMjHgQFJa a7BA==
X-Gm-Message-State ALoCoQnelKEuKhFESXXhOtxtkwslS4AZ41/il6vM14mSHJQYG+5YFxGLkBfoNsVQ/kV0GWnTPg0e
MIME-Version 1.0
X-Received by 10.152.45.41 with SMTP id j9mr2814606lam.110.1442309923779; Tue, 15 Sep 2015 02:38:43 -0700 (PDT)
Content-Type text/plain; charset=UTF-8
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 133
Organization linux.* mail to news gateway
X-Original-Cc Alex Smith <alex.smith@imgtec.com>, linux-mtd@lists.infradead.org, Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>, David Woodhouse <dwmw2@infradead.org>, linux-kernel@vger.kernel.org
X-Original-Date Tue, 15 Sep 2015 10:38:43 +0100
X-Original-Message-ID <CAOFt0_DK+KDe4g2QP-+v0nZiSWU0oaLW7=B+WfzNHq-GHwg=BA@mail.gmail.com>
X-Original-References <1441703453-2838-1-git-send-email-alex.smith@imgtec.com> <1441703453-2838-2-git-send-email-alex.smith@imgtec.com> <20150909234936.GB11487@google.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1224918

Show key headers only | View raw


On 10 September 2015 at 00:49, Brian Norris <computersforpeace@gmail.com> wrote:
> + Niklas
>
> On Tue, Sep 08, 2015 at 10:10:50AM +0100, Alex Smith wrote:
>> If nand_wait_ready() times out, this is silently ignored, and its
>> caller will then proceed to read from/write to the chip before it is
>> ready. This can potentially result in corruption with no indication as
>> to why.
>>
>> While a 20ms timeout seems like it should be plenty enough, certain
>> behaviour can cause it to timeout much earlier than expected. The
>> situation which prompted this change was that CPU 0, which is
>> responsible for updating jiffies, was holding interrupts disabled
>> for a fairly long time while writing to the console during a printk,
>> causing several jiffies updates to be delayed. If CPU 1 happens to
>> enter the timeout loop in nand_wait_ready() just before CPU 0 re-
>> enables interrupts and updates jiffies, CPU 1 will immediately time
>> out when the delayed jiffies updates are made. The result of this is
>> that nand_wait_ready() actually waits less time than the NAND chip
>> would normally take to be ready, and then read_page() proceeds to
>> read out bad data from the chip.
>>
>> The situation described above may seem unlikely, but in fact it can be
>> reproduced almost every boot on the MIPS Creator Ci20.
>>
>> Debugging this was made more difficult by the misleading comment above
>> nand_wait_ready() stating "The timeout is caught later" - no timeout
>> was ever reported, leading me away from the real source of the problem.
>>
>> Therefore, this patch increases the timeout to 200ms. This should be
>> enough to cover cases where jiffies updates get delayed. Additionally,
>> add a pr_warn() when a timeout does occur so that it is easier to
>> pinpoint any problems in future caused by the chip not becoming ready.
>
> Did you examine other solutions? I've seen patches for hrtimer support
> previously:
>
> http://patchwork.ozlabs.org/patch/160333/
> http://patchwork.ozlabs.org/patch/431066/
>
> A few things have been cleaned up since then, so some of the initial
> objections to the hrtimer patch don't make sense anymore, I believe.
>
> Anyway, I think just increasing the timeout looks OK to me (as long as
> we never have a 200ms jiffies jump... can this happen??), so hrtimer may
> be over-engineering. I just want to make sure both options have been
> considered before officially choosing one over the other.
>
> Brian

Hi Brian, Niklas,

I'm no expert in the matter but I feel like using a hrtimer here would
indeed be over-engineering and could potentially add overhead to the
"normal" case where the chip becomes ready well before the timeout
expires? Just increasing the timeout seems like a simpler solution
that solves the problem. I think that a jiffies jump of a few hundred
milliseconds is extremely unlikely and would indicate something else
that needs to be fixed (i.e. in the SMP case I had it would mean that
the CPU which is supposed to update jiffies has interrupts disabled
for hundreds of milliseconds).

Niklas: If I update the patch based on your suggestions would you be
happy to go with that rather than your hrtimer patch?

Thanks,
Alex

>
>> Signed-off-by: Alex Smith <alex.smith@imgtec.com>
>> Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
>> Cc: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
>> Cc: David Woodhouse <dwmw2@infradead.org>
>> Cc: Brian Norris <computersforpeace@gmail.com>
>> Cc: linux-mtd@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> ---
>> v4 -> v5:
>>  - Remove spurious change.
>>  - Add Ezequiel's Reviewed-by.
>>
>> v3 -> v4:
>>  - New patch to fix issue encountered in external Ci20 3.18 kernel
>>    branch which also applies upstream.
>> ---
>>  drivers/mtd/nand/nand_base.c | 14 +++++++++++---
>>  1 file changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
>> index ceb68ca8277a..07b831b94e5c 100644
>> --- a/drivers/mtd/nand/nand_base.c
>> +++ b/drivers/mtd/nand/nand_base.c
>> @@ -543,11 +543,16 @@ static void panic_nand_wait_ready(struct mtd_info *mtd, unsigned long timeo)
>>       }
>>  }
>>
>> -/* Wait for the ready pin, after a command. The timeout is caught later. */
>> +/**
>> + * nand_wait_ready - [GENERIC] Wait for the ready pin after commands.
>> + * @mtd: MTD device structure
>> + *
>> + * Wait for the ready pin after a command, and warn if a timeout occurs.
>> + */
>>  void nand_wait_ready(struct mtd_info *mtd)
>>  {
>>       struct nand_chip *chip = mtd->priv;
>> -     unsigned long timeo = jiffies + msecs_to_jiffies(20);
>> +     unsigned long timeo = jiffies + msecs_to_jiffies(200);
>>
>>       /* 400ms timeout */
>>       if (in_interrupt() || oops_in_progress)
>> @@ -557,9 +562,12 @@ void nand_wait_ready(struct mtd_info *mtd)
>>       /* Wait until command is processed or timeout occurs */
>>       do {
>>               if (chip->dev_ready(mtd))
>> -                     break;
>> +                     goto out;
>>               touch_softlockup_watchdog();
>>       } while (time_before(jiffies, timeo));
>> +
>> +     pr_warn("timeout while waiting for chip to become ready\n");
>> +out:
>>       led_trigger_event(nand_led_trigger, LED_OFF);
>>  }
>>  EXPORT_SYMBOL_GPL(nand_wait_ready);
>> --
>> 2.5.0
>>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v5 1/4] mtd: nand: increase ready wait timeout and report timeouts Alex Smith <alex.smith@imgtec.com> - 2015-09-08 11:20 +0200
  Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report  timeouts Brian Norris <computersforpeace@gmail.com> - 2015-09-10 01:50 +0200
    Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report  timeouts Niklas Cassel <niklas.cassel@axis.com> - 2015-09-11 13:40 +0200
    Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report timeouts Alex Smith <alex@alex-smith.me.uk> - 2015-09-15 11:40 +0200
      Re: [PATCH v5 1/4] mtd: nand: increase ready wait timeout and report  timeouts Niklas Cassel <niklas.cassel@axis.com> - 2015-09-15 12:00 +0200

csiph-web