summaryrefslogtreecommitdiff
path: root/.get_maintainer.ignore
diff options
context:
space:
mode:
authorLeonid Iziumtsev <leonid.iziumtsev@gmail.com>2019-01-15 17:15:23 +0000
committerVinod Koul <vkoul@kernel.org>2019-02-04 12:35:12 +0530
commit341198eda723c8c1cddbb006a89ad9e362502ea2 (patch)
tree915e69ff12f1e7566caa5d64254f09dcc15a020b /.get_maintainer.ignore
parentdc3f595b6617ebc0307e0ce151e8f2f2b2489b95 (diff)
dmaengine: imx-dma: fix wrong callback invoke
Once the "ld_queue" list is not empty, next descriptor will migrate into "ld_active" list. The "desc" variable will be overwritten during that transition. And later the dmaengine_desc_get_callback_invoke() will use it as an argument. As result we invoke wrong callback. That behaviour was in place since: commit fcaaba6c7136 ("dmaengine: imx-dma: fix callback path in tasklet"). But after commit 4cd13c21b207 ("softirq: Let ksoftirqd do its job") things got worse, since possible delay between tasklet_schedule() from DMA irq handler and actual tasklet function execution got bigger. And that gave more time for new DMA request to be submitted and to be put into "ld_queue" list. It has been noticed that DMA issue is causing problems for "mxc-mmc" driver. While stressing the system with heavy network traffic and writing/reading to/from sd card simultaneously the timeout may happen: 10013000.sdhci: mxcmci_watchdog: read time out (status = 0x30004900) That often lead to file system corruption. Signed-off-by: Leonid Iziumtsev <leonid.iziumtsev@gmail.com> Signed-off-by: Vinod Koul <vkoul@kernel.org> Cc: stable@vger.kernel.org
Diffstat (limited to '.get_maintainer.ignore')
0 files changed, 0 insertions, 0 deletions