From: Johan Hovold <johan@kernel.org>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Ma Ke <make24@iscas.ac.cn>,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/2] drm/mediatek: fix potential OF node use-after-free
Date: Fri, 29 Aug 2025 11:03:43 +0200 [thread overview]
Message-ID: <20250829090345.21075-1-johan@kernel.org> (raw)
A recent change (included in the drm pull request for 6.17-rc4) fixed a
device reference leak but also introduced a potential OF node
use-after-free.
This series fixes the new OF node reference imbalance and drops the
unnecessary gotos introduced by the broken fix, effectively reverting
that change in favour of the minimal fix I had previously posted here:
https://lore.kernel.org/lkml/20250722092722.425-1-johan@kernel.org/
These should go into 6.17 which (soon) has the broken fix, which was
also marked for stable backport.
Johan
Johan Hovold (2):
drm/mediatek: fix potential OF node use-after-free
drm/mediatek: clean up driver data initialisation
drivers/gpu/drm/mediatek/mtk_drm_drv.c | 23 +++++++++--------------
1 file changed, 9 insertions(+), 14 deletions(-)
--
2.49.1
next reply other threads:[~2025-08-29 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 9:03 Johan Hovold [this message]
2025-08-29 9:03 ` [PATCH 1/2] drm/mediatek: fix potential OF node use-after-free Johan Hovold
2025-09-08 3:41 ` CK Hu (胡俊光)
2025-09-08 3:41 ` CK Hu (胡俊光)
2025-08-29 9:03 ` [PATCH 2/2] drm/mediatek: clean up driver data initialisation Johan Hovold
2025-09-10 1:38 ` CK Hu (胡俊光)
2025-09-10 1:38 ` CK Hu (胡俊光)
2025-09-10 9:33 ` [PATCH 0/2] drm/mediatek: fix potential OF node use-after-free AngeloGioacchino Del Regno
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=20250829090345.21075-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=make24@iscas.ac.cn \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=simona@ffwll.ch \
/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.