From: Ludovic Desroches <ludovic.desroches@microchip.com>
To: Manikandan Muralidharan <manikandan.m@microchip.com>,
"Dharma Balasubiramani" <dharma.b@microchip.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: <dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: [PATCH 0/2] drm/atmel-hlcdc: fix memory bugs
Date: Fri, 24 Oct 2025 18:14:51 +0200 [thread overview]
Message-ID: <20251024-lcd_fixes_mainlining-v1-0-79b615130dc3@microchip.com> (raw)
These two patches fix a memory leak and a use after free bugs.
The memory leak bug had been reported by several users. There were some
attempts to fix it in the past, but the resolutions proposed caused
other breakages.
Signed-off-by: Ludovic Desroches <ludovic.desroches@microchip.com>
---
Ludovic Desroches (2):
drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback
drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
---
base-commit: 72fb0170ef1f45addf726319c52a0562b6913707
change-id: 20251024-lcd_fixes_mainlining-a1234d81a768
Best regards,
--
Ludovic Desroches <ludovic.desroches@microchip.com>
next reply other threads:[~2025-10-24 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 16:14 Ludovic Desroches [this message]
2025-10-24 16:14 ` [PATCH 1/2] drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback Ludovic Desroches
2025-10-24 16:14 ` [PATCH 2/2] drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release Ludovic Desroches
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=20251024-lcd_fixes_mainlining-v1-0-79b615130dc3@microchip.com \
--to=ludovic.desroches@microchip.com \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dharma.b@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=manikandan.m@microchip.com \
--cc=mripard@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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).