From: "Michał Grzelak" <michal.grzelak@intel.com>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Michał Grzelak" <michal.grzelak@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Matthew Auld" <matthew.auld@intel.com>
Subject: [RESEND 1/1] drm/buddy: release free_trees array on buddy mm teardown
Date: Mon, 8 Dec 2025 11:27:14 +0100 [thread overview]
Message-ID: <20251208102714.4008260-2-michal.grzelak@intel.com> (raw)
In-Reply-To: <20251208102714.4008260-1-michal.grzelak@intel.com>
During initialization of DRM buddy memory manager at drm_buddy_init,
mm->free_trees array is allocated for both clear and dirty RB trees.
During cleanup happening at drm_buddy_fini it is never freed, leading to
following memory leaks observed on xe module load & unload cycles:
kmemleak_alloc+0x4a/0x90
__kmalloc_cache_noprof+0x488/0x800
drm_buddy_init+0xc2/0x330 [drm_buddy]
__xe_ttm_vram_mgr_init+0xc3/0x190 [xe]
xe_ttm_stolen_mgr_init+0xf5/0x9d0 [xe]
xe_device_probe+0x326/0x9e0 [xe]
xe_pci_probe+0x39a/0x610 [xe]
local_pci_probe+0x47/0xb0
pci_device_probe+0xf3/0x260
really_probe+0xf1/0x3c0
__driver_probe_device+0x8c/0x180
driver_probe_device+0x24/0xd0
__driver_attach+0x10f/0x220
bus_for_each_dev+0x7f/0xe0
driver_attach+0x1e/0x30
bus_add_driver+0x151/0x290
Deallocate array for free trees when cleaning up buddy memory manager
in the same way as if going through out_free_tree label.
Fixes: d4cd665c98c1 ("drm/buddy: Separate clear and dirty free block trees")
Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
---
drivers/gpu/drm/drm_buddy.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
index 2f279b46bd2c..8308116058cc 100644
--- a/drivers/gpu/drm/drm_buddy.c
+++ b/drivers/gpu/drm/drm_buddy.c
@@ -420,6 +420,7 @@ void drm_buddy_fini(struct drm_buddy *mm)
for_each_free_tree(i)
kfree(mm->free_trees[i]);
+ kfree(mm->free_trees);
kfree(mm->roots);
}
EXPORT_SYMBOL(drm_buddy_fini);
--
2.45.2
next prev parent reply other threads:[~2025-12-08 10:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 10:27 [RESEND 0/1] drm/buddy: release free_trees array on buddy mm teardown Michał Grzelak
2025-12-08 10:27 ` Michał Grzelak [this message]
2025-12-08 14:16 ` ✓ CI.KUnit: success for drm/buddy: release free_trees array on buddy mm teardown (rev3) Patchwork
2025-12-08 15:17 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-08 20:09 ` ✗ Xe.CI.Full: failure " Patchwork
2025-12-09 22:07 ` Michał Grzelak
-- strict thread matches above, loose matches on Subject: below --
2025-12-19 19:32 [RESEND 1/1] drm/buddy: release free_trees array on buddy mm teardown Michał Grzelak
2025-12-19 20:38 ` Lin, Shuicheng
2025-12-23 7:35 ` Michał Grzelak
2025-12-23 17:14 ` Lin, Shuicheng
2026-01-19 16:25 ` Matthew Auld
2026-01-20 5:27 ` Arunpravin Paneer Selvam
2026-01-20 10:40 ` Matthew Auld
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=20251208102714.4008260-2-michal.grzelak@intel.com \
--to=michal.grzelak@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=mripard@kernel.org \
--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