diff options
| author | Daniel Golle <daniel@makrotopia.org> | 2022-03-21 01:16:48 +0000 |
|---|---|---|
| committer | Paul Spooren <mail@aparcar.org> | 2022-03-21 11:36:30 +0000 |
| commit | 3a14580411adfb75f9a44eded9f41245b9e44606 (patch) | |
| tree | c3002cc1a0948bfedc4475d7276da0b3ebd4775c /target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch | |
| parent | 9f9477b2751231d57cdd8c227149b88c93491d93 (diff) | |
| download | upstream-3a14580411adfb75f9a44eded9f41245b9e44606.tar.gz upstream-3a14580411adfb75f9a44eded9f41245b9e44606.tar.bz2 upstream-3a14580411adfb75f9a44eded9f41245b9e44606.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>
Diffstat (limited to 'target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch')
| -rw-r--r-- | target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch | 37 |
1 files changed, 0 insertions, 37 deletions
diff --git a/target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch b/target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch deleted file mode 100644 index b28f7b172c..0000000000 --- a/target/linux/layerscape/patches-5.4/805-display-0046-MLK-22171-drm-imx-Avoid-leaking-dangling-pointer-dev.patch +++ /dev/null @@ -1,37 +0,0 @@ -From 98917e88ec975eee0194ca011479e507029009ae Mon Sep 17 00:00:00 2001 -From: Liu Ying <victor.liu@nxp.com> -Date: Tue, 30 Jul 2019 13:13:16 +0800 -Subject: [PATCH] MLK-22171 drm/imx: Avoid leaking dangling pointer - dev->driver_data to PM ops - -In case ->bind() fails, we should avoid leaking dangling pointer -dev->driver_data which is set by dev_set_drvdata(), otherwise -it would be leaked, and seen/dereferenced by PM ops, thus hang -happens. Moving dev_set_drvdata() down just before ->bind() -successfully returns may address this issue. - -Signed-off-by: Liu Ying <victor.liu@nxp.com> ---- - drivers/gpu/drm/imx/imx-drm-core.c | 4 ++-- - 1 file changed, 2 insertions(+), 2 deletions(-) - ---- a/drivers/gpu/drm/imx/imx-drm-core.c -+++ b/drivers/gpu/drm/imx/imx-drm-core.c -@@ -239,8 +239,6 @@ static int imx_drm_bind(struct device *d - if (ret) - goto err_kms; - -- dev_set_drvdata(dev, drm); -- - /* Now try and bind all our sub-components */ - ret = component_bind_all(dev, drm); - if (ret) -@@ -266,6 +264,8 @@ static int imx_drm_bind(struct device *d - - drm_fbdev_generic_setup(drm, legacyfb_depth); - -+ dev_set_drvdata(dev, drm); -+ - return 0; - - err_poll_fini: |