From: sashiko-bot@kernel.org
To: "Maxime Ripard" <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 13/61] drm/amdgpu: Convert to atomic_create_state
Date: Fri, 14 Aug 2026 15:14:14 +0000 [thread overview]
Message-ID: <20260814151415.4B9131F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814-drm-no-more-plane-reset-v2-13-82d2963dd134@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The dynamically allocated `drm_plane` structures for AMDGPU VKMS are never freed, causing a memory leak during driver teardown and on initialization error paths.
--
--- Patch [13]: [PATCH v2 13/61] drm/amdgpu: Convert to atomic_create_state ---
commit e8c110baf25c9fbe2352593883aad5a81fdc938b
Author: Maxime Ripard <mripard@kernel.org>
drm/amdgpu: Convert to atomic_create_state
This patch converts the reset hook to atomic_create_state for the plane.
This allows the plane to initialize a pristine state using
drm_atomic_helper_plane_reset(), matching what atomic_create_state expects.
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vkms.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vkms.c
> index 170adaf7e76ab..9628239855d23 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vkms.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vkms.c
> @@ -144,7 +144,7 @@ static const struct drm_plane_funcs amdgpu_vkms_plane_funcs = {
> .update_plane = drm_atomic_helper_update_plane,
> .disable_plane = drm_atomic_helper_disable_plane,
> .destroy = drm_plane_cleanup,
[Severity: High]
This isn't a bug introduced by this patch, but does this code leak the
dynamically allocated plane structure?
The .destroy hook is mapped directly to drm_plane_cleanup(), which tears down
DRM internal objects but does not free the enclosing structure.
In amdgpu_vkms_plane_init(), the plane is dynamically allocated, but during
driver teardown the DRM core iterates over the planes and calls this .destroy
hook, which fails to free the memory. Similarly, this memory appears to leak
on the error path in amdgpu_vkms_output_init():
amdgpu_vkms_output_init() {
...
err_crtc:
drm_plane_cleanup(primary);
return ret;
}
Should there be a custom destroy hook that calls drm_plane_cleanup() followed
by kfree() to prevent this leak?
> - .reset = drm_atomic_helper_plane_reset,
> + .atomic_create_state = drm_atomic_helper_plane_create_state,
> .atomic_duplicate_state = drm_atomic_helper_plane_duplicate_state,
> .atomic_destroy_state = drm_atomic_helper_plane_destroy_state,
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260814-drm-no-more-plane-reset-v2-0-82d2963dd134@kernel.org?part=13
next prev parent reply other threads:[~2026-08-14 15:14 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 14:56 [PATCH v2 00/61] drm/plane: Convert all drivers to atomic_create_state and remove reset Maxime Ripard
2026-08-14 14:56 ` Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 01/61] drm/simple-kms: Add create_plane_state hook Maxime Ripard
2026-08-14 15:13 ` sashiko-bot
2026-08-14 14:56 ` [PATCH v2 02/61] drm/gem-atomic-helper: Create drm_gem_create_shadow_plane_state() Maxime Ripard
2026-08-14 15:11 ` sashiko-bot
2026-08-14 14:56 ` [PATCH v2 03/61] drm/gem-atomic-helper: Convert simple-kms shadow helpers to create_plane_state Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 04/61] drm/gem-atomic-helper: Switch DRM_GEM_SHADOW_PLANE_FUNCS to atomic_create_state Maxime Ripard
2026-08-14 15:11 ` sashiko-bot
2026-08-14 14:56 ` [PATCH v2 05/61] drm/gem-atomic-helper: Remove drm_gem_reset_shadow_plane() Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 06/61] drm/sysfb: Convert to atomic_create_state Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 07/61] drm/simple-kms: Switch " Maxime Ripard
2026-08-14 15:10 ` sashiko-bot
2026-08-14 14:56 ` [PATCH v2 08/61] drm/ssd130x: Convert " Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 09/61] drm/st7920: " Maxime Ripard
2026-08-14 14:56 ` [PATCH v2 10/61] drm/appletbdrm: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 11/61] drm/vkms: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 12/61] drm/gem-atomic-helper: Remove __drm_gem_reset_shadow_plane() Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 13/61] drm/amdgpu: Convert to atomic_create_state Maxime Ripard
2026-08-14 15:14 ` sashiko-bot [this message]
2026-08-14 14:57 ` [PATCH v2 14/61] drm/hdlcd: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 15/61] drm/fsl-dcu: " Maxime Ripard
2026-08-14 15:08 ` sashiko-bot
2026-08-14 14:57 ` [PATCH v2 16/61] drm/hisilicon/kirin: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 17/61] drm/imx/dc: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 18/61] drm/imx/dcss: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 19/61] drm/ingenic: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 20/61] drm/kmb: " Maxime Ripard
2026-08-14 15:14 ` sashiko-bot
2026-08-14 14:57 ` [PATCH v2 21/61] drm/logicvc: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 22/61] drm/loongson: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 23/61] drm/meson: " Maxime Ripard
2026-08-14 14:57 ` Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 24/61] drm/msm/mdp4: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 25/61] drm/lcdif: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 26/61] drm/mxsfb: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 27/61] drm/qxl: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 28/61] drm/rockchip: " Maxime Ripard
2026-08-14 14:57 ` Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 29/61] drm/sprd: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 30/61] drm/sti: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 31/61] drm/stm: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 32/61] drm/sun4i: sun8i: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 33/61] drm/tests: kunit: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 34/61] drm/tilcdc: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 35/61] drm/vboxvideo: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 36/61] drm/verisilicon: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 37/61] drm/virtio: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 38/61] drm/xlnx: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 39/61] drm/atomic-state-helper: Remove drm_atomic_helper_plane_reset() Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 40/61] drm/amdgpu_dm: Convert to atomic_create_state Maxime Ripard
2026-08-14 15:25 ` sashiko-bot
2026-08-14 14:57 ` [PATCH v2 41/61] drm/komeda: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 42/61] drm/malidp: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 43/61] drm/armada: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 44/61] drm/atmel-hlcdc: Drop spurious csc_init call from reset Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 45/61] drm/atmel-hlcdc: Convert to atomic_create_state Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 46/61] drm/exynos: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 47/61] drm/imx/ipuv3: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 48/61] drm/mediatek: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 49/61] drm/msm/dpu1: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 50/61] drm/msm/mdp5: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 51/61] drm/nouveau: " Maxime Ripard
2026-08-14 14:57 ` Maxime Ripard
2026-08-14 19:06 ` lyude
2026-08-14 14:57 ` [PATCH v2 52/61] drm/omap: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 53/61] drm/rcar-du: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 54/61] drm/rz-du: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 55/61] drm/shmobile: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 56/61] drm/sun4i: layer: " Maxime Ripard
2026-08-14 15:28 ` sashiko-bot
2026-08-14 14:57 ` [PATCH v2 57/61] drm/vc4: " Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 58/61] drm/vmwgfx: " Maxime Ripard
2026-08-14 15:30 ` sashiko-bot
2026-08-14 14:57 ` [PATCH v2 59/61] drm/atomic-state-helper: Remove __drm_atomic_helper_plane_reset() Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 60/61] drm/tegra: Convert to atomic_create_state Maxime Ripard
2026-08-14 14:57 ` [PATCH v2 61/61] drm/plane: Remove reset Maxime Ripard
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=20260814151415.4B9131F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=mripard@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.