linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org,
	linux-sh@vger.kernel.org, max.filippov@cogentembedded.com
Subject: Re: [PATCH v2] tmio_mmc_dma: fix PIO fallback on SDHI
Date: Mon, 05 Aug 2013 22:37:19 +0000	[thread overview]
Message-ID: <5200291F.2020607@cogentembedded.com> (raw)
In-Reply-To: <51FE60DF.400@cogentembedded.com>

Hello.

On 08/04/2013 06:10 PM, Sergei Shtylyov wrote:

>>> I'm testing SH-Mobile SDHI driver in DMA mode with  a new DMA controller
>>> using
>>> 'bonnie++' and getting DMA error after which the tmio_mmc_dma.c code falls
>>> back
>>> to PIO but all commands time out after that.  It turned out that the fallback
>>> code calls tmio_mmc_enable_dma() with RX/TX channels already freed and
>>> pointers
>>> to them cleared, so that the function bails out early instead  of clearing the
>>> DMA bit in the CTL_DMA_ENABLE register. The regression was introduced by
>>> commit
>>> 162f43e31c5a376ec16336e5d0ac973373d54c89 (mmc: tmio: fix a deadlock).
>>> Moving tmio_mmc_enable_dma() calls to the top of the PIO fallback code in
>>> tmio_mmc_start_dma_{rx|tx}() helps.

>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Cc: stable@vger.kernel.org # 3.1+

>> Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>

>> Not sure though how far back in stable this really has to go. We don't
>> have any real-life problem reports with older kernels, do we?

>     If we did, that error would have been fixed earlier, wouldn't it?

>> I think
>> approach to which patches should get into stable changed recently.

>     Haven't heard about that (or seen any change in the policy). The issue
> with this bug is its catastrophic consequencies: you can hardly ^C or ^Z out
> of 'bonnie++' when it happens (in fact, you cannot ^C at all). IIRC you can't
> even kill it from another shell.

    Yeah, and the filesystem is seriously corrupt after this (I've tested only 
on VFAT so far).

>> Thanks
>> Guennadi

WBR, Sergei


  reply	other threads:[~2013-08-05 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 22:33 [PATCH v2] tmio_mmc_dma: fix PIO fallback on SDHI Sergei Shtylyov
2013-08-03 22:36 ` Guennadi Liakhovetski
2013-08-04 14:10   ` Sergei Shtylyov
2013-08-05 22:37     ` Sergei Shtylyov [this message]
2013-08-09 18:41       ` Sergei Shtylyov
2013-08-25  3:39   ` Chris Ball
2013-08-09 18:32 ` Sergei Shtylyov

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=5200291F.2020607@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=cjb@laptop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=max.filippov@cogentembedded.com \
    /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).