From: no-reply@sashiko.virtuozzo.com
To: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>,
khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ms/drm/buddy: release free_trees array on buddy mm teardown
Date: Mon, 16 Nov 2026 03:32:16 +0000 [thread overview]
Message-ID: <010701a1e269a53f-40de841f-bf60-4b8d-acd8-cdd6073b273f-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261116032734.24795-1-mirian.shilakadze@virtuozzo.com>
> From: Michał Grzelak <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
> [ ... ]
>
> https://virtuozzo.atlassian.net/browse/VSTOR-154850
> Feature: fix ms/drm
>
> Signed-off-by: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261116032734.24795-1-mirian.shilakadze@virtuozzo.com?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-16 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 3:27 Mirian Shilakadze
2026-11-16 3:32 ` no-reply [this message]
2026-11-16 15:59 ` Konstantin Khorenko
2026-11-16 15:59 ` Konstantin Khorenko
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=010701a1e269a53f-40de841f-bf60-4b8d-acd8-cdd6073b273f-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=mirian.shilakadze@virtuozzo.com \
/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.