From: Michael Grzeschik <m.grzeschik@pengutronix.de>
To: p.zabel@pengutronix.de, airlied@linux.ie, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
dri-devel@lists.freedesktop.org, rafael@kernel.org,
kernel@pengutronix.de
Subject: [PATCH 0/3] Fix for drm_mode_config_cleanup issue
Date: Tue, 2 Apr 2019 15:49:01 +0200 [thread overview]
Message-ID: <20190402134904.588-1-m.grzeschik@pengutronix.de> (raw)
In-Reply-To: <0687f68004b28ed3a364b06a9eb64e2e@agner.ch>
Fix the issue: "drm/imx: Crash in drm_mode_config_cleanup".
Which was documented here:
https://www.spinics.net/lists/dri-devel/msg189388.html
And tried to address with this:
https://patchwork.kernel.org/patch/10633297/
https://patchwork.kernel.org/patch/10633299/
This series fixes the possible case of use after free by adding action
functions to the devres cleanup path. So it will ensure the generic
cleanup code will not use the already freed memory.
Michael Grzeschik (3):
ipuv3-crtc: add remove action for devres data
ipuv3-ldb: add init list head on bind
ipuv3-ldb: add remove action for devres data
drivers/gpu/drm/imx/imx-ldb.c | 35 ++++++++++++++++++++++++++++++++
drivers/gpu/drm/imx/ipuv3-crtc.c | 12 +++++++++++
2 files changed, 47 insertions(+)
--
2.20.1
next parent reply other threads:[~2019-04-02 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0687f68004b28ed3a364b06a9eb64e2e@agner.ch>
2019-04-02 13:49 ` Michael Grzeschik [this message]
2019-04-02 13:49 ` [PATCH 1/3] ipuv3-crtc: add remove action for devres data Michael Grzeschik
2019-04-02 15:49 ` Philipp Zabel
2019-04-03 7:22 ` Daniel Vetter
2019-04-02 13:49 ` [PATCH 2/3] ipuv3-ldb: add init list head on bind Michael Grzeschik
2019-04-02 13:49 ` [PATCH 3/3] ipuv3-ldb: add remove action for devres data Michael Grzeschik
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=20190402134904.588-1-m.grzeschik@pengutronix.de \
--to=m.grzeschik@pengutronix.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=p.zabel@pengutronix.de \
--cc=rafael@kernel.org \
/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).