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 1/1] ms/drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()
Date: Fri, 6 Nov 2026 15:00:07 +0000 [thread overview]
Message-ID: <010701a1b15fc91e-ff281274-8f76-43b0-a98b-bcefff2eede0-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261106145524.96305-2-mirian.shilakadze@virtuozzo.com>
> From: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> drmm_cgroup_register_region() is called before INIT_LIST_HEAD() and
> gpu_buddy_init() in amdgpu_vram_mgr_init(). If it fails, the function
> returns early and bypasses those initializations.
>
> Since adev->mman.initialized is set to true before amdgpu_vram_mgr_init()
> is called, a failure triggers amdgpu_ttm_fini(), which calls
> amdgpu_vram_mgr_fini(), which then:
>
> - Calls list_for_each_entry_safe() on reservations_pending and
> reserved_pages, whose list_head::next pointers are zero-initialized
> (NULL). The loop does not recognize them as empty and dereferences NULL.
>
> - Calls gpu_buddy_fini(), which iterates free_trees[] unconditionally
> [ ... ]
>
> https://virtuozzo.atlassian.net/browse/VSTOR-153702
> Feature: fix ms/drm
>
> Signed-off-by: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261106145524.96305-1-mirian.shilakadze@virtuozzo.com?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-06 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 14:55 [Devel] [PATCH hci-8.1 0/1] drm/amdgpu: fix " Mirian Shilakadze
2026-11-06 14:55 ` [Devel] [PATCH hci-8.1 1/1] ms/drm/amdgpu: Fix " Mirian Shilakadze
2026-11-06 15:00 ` no-reply [this message]
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=010701a1b15fc91e-ff281274-8f76-43b0-a98b-bcefff2eede0-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox