From: Wen Yang <wen.yang99@zte.com.cn>
To: linux-kernel@vger.kernel.org
Cc: wang.yi59@zte.com.cn, Wen Yang <wen.yang99@zte.com.cn>
Subject: [PATCH 0/7] fix possible object reference leaks in drivers/gpu
Date: Thu, 4 Apr 2019 00:04:08 +0800 [thread overview]
Message-ID: <1554307455-40361-1-git-send-email-wen.yang99@zte.com.cn> (raw)
The call to of_get_cpu_node/of_find_compatible_node/of_parse_phandle...
returns a node pointer with refcount incremented thus it must be
explicitly decremented after the last usage.
This patch series fix those possible object reference leaks in drivers/gpu.
Wen Yang (7):
drm/mediatek: fix possible object reference leak
drm/meson: fix possible object reference leak
drm/msm: a5xx: fix possible object reference leak
drm/omap: fix possible object reference leak
drm/pl111: fix possible object reference leak
drm: rcar-du: fix possible object reference leak
drm/tegra: fix possible object reference leak
drivers/gpu/drm/mediatek/mtk_hdmi.c | 1 +
drivers/gpu/drm/meson/meson_dw_hdmi.c | 7 ++-----
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 10 ++++++----
drivers/gpu/drm/omapdrm/dss/omapdss-boot-init.c | 5 ++++-
drivers/gpu/drm/pl111/pl111_versatile.c | 4 ++++
drivers/gpu/drm/rcar-du/rcar_du_of.c | 2 ++
drivers/gpu/drm/tegra/output.c | 2 ++
drivers/gpu/drm/tegra/rgb.c | 8 ++++++--
8 files changed, 27 insertions(+), 12 deletions(-)
--
2.9.5
next reply other threads:[~2019-04-03 16:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:04 Wen Yang [this message]
2019-04-03 16:04 ` [PATCH 1/7] drm/mediatek: fix possible object reference leak Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-09 5:15 ` CK Hu
2019-04-09 5:15 ` CK Hu
2019-04-09 5:15 ` CK Hu
2019-04-03 16:04 ` [PATCH 2/7] drm/meson: " Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-04 20:05 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 3/7] drm/msm: a5xx: " Wen Yang
2019-04-10 16:21 ` Jordan Crouse
2019-04-10 16:21 ` Jordan Crouse
2019-04-03 16:04 ` [PATCH 4/7] drm/omap: " Wen Yang
2019-04-04 13:25 ` Laurent Pinchart
2019-04-08 1:24 ` wen.yang99
2019-04-04 20:42 ` Markus Elfring
2019-04-04 20:42 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 5/7] drm/pl111: " Wen Yang
2019-04-03 16:04 ` Wen Yang
2019-04-04 19:59 ` Eric Anholt
2019-04-04 19:59 ` Eric Anholt
2019-04-04 21:05 ` Markus Elfring
2019-04-04 21:05 ` Markus Elfring
2019-04-03 16:04 ` [PATCH 6/7] drm: rcar-du: " Wen Yang
2019-04-04 13:35 ` Laurent Pinchart
2019-04-08 1:10 ` 答复: " wen.yang99
2019-04-03 16:04 ` [PATCH 7/7] drm/tegra: " Wen Yang
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=1554307455-40361-1-git-send-email-wen.yang99@zte.com.cn \
--to=wen.yang99@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=wang.yi59@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.