diff options
author | Daniel Golle <daniel@makrotopia.org> | 2022-03-21 01:16:48 +0000 |
---|---|---|
committer | Daniel Golle <daniel@makrotopia.org> | 2022-03-21 13:11:56 +0000 |
commit | 786bf7fdaca4c75e7eba6e9aa3a8b5775fd21186 (patch) | |
tree | 926fecb2b1f6ce1e42ba7ef4c7aab8e68dfd214c /target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch | |
parent | 9470160c350d15f765c33d6c1db15d6c4709a64c (diff) | |
download | upstream-786bf7fdaca4c75e7eba6e9aa3a8b5775fd21186.tar.gz upstream-786bf7fdaca4c75e7eba6e9aa3a8b5775fd21186.tar.bz2 upstream-786bf7fdaca4c75e7eba6e9aa3a8b5775fd21186.zip |
kernel: delete Linux 5.4 config and patches
As the upcoming release will be based on Linux 5.10 only, remove all
kernel configuration as well as patches for Linux 5.4.
There were no targets still actively using Linux 5.4.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
(cherry picked from commit 3a14580411adfb75f9a44eded9f41245b9e44606)
Diffstat (limited to 'target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch')
-rw-r--r-- | target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch b/target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch deleted file mode 100644 index 28a59d4db2..0000000000 --- a/target/linux/layerscape/patches-5.4/806-dma-0016-MLK-19931-1-dmaengine-fsl-edma-v3-fix-potential-kern.patch +++ /dev/null @@ -1,33 +0,0 @@ -From 4967ec844a52498af050b1176fedeca37aca111e Mon Sep 17 00:00:00 2001 -From: Robin Gong <yibin.gong@nxp.com> -Date: Tue, 16 Oct 2018 01:06:29 +0800 -Subject: [PATCH] MLK-19931-1: dmaengine: fsl-edma-v3: fix potential kernel - crash in cyclic - - There is one potential race condition in virt-dma framework as below: -terminate dma channel after the last dma done interrupt, but before -vchan_complete tasklet scheduled, thus the free-ed 'vd' (free in -fsl_edma3_terminate_all) maybe still be touched in vchan_complete() -which cause NULL pointer crash. - Kernel community noticed this issue and fix it at virt-dma level: -https://patchwork.kernel.org/patch/10057791/. To avoid backport too -much patches, set 'vc->cyclic = NULL' in terminate dma channel -interfaces to fix such issue easily. - -Signed-off-by: Robin Gong <yibin.gong@nxp.com> -Acked-by: Fugang Duan <fugang.duan@nxp.com> -(cherry picked from commit 18c9083826400a2ef731496391a0b5e71d461a5f) ---- - drivers/dma/fsl-edma-v3.c | 1 + - 1 file changed, 1 insertion(+) - ---- a/drivers/dma/fsl-edma-v3.c -+++ b/drivers/dma/fsl-edma-v3.c -@@ -285,6 +285,7 @@ static int fsl_edma3_terminate_all(struc - fsl_chan->edesc = NULL; - fsl_chan->idle = true; - fsl_chan->used = false; -+ fsl_chan->vchan.cyclic = NULL; - vchan_get_all_descriptors(&fsl_chan->vchan, &head); - spin_unlock_irqrestore(&fsl_chan->vchan.lock, flags); - vchan_dma_desc_free_list(&fsl_chan->vchan, &head); |