From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/6] cgroup/dmem: backport fixes and apply a lower dmem.max at once
Date: Thu, 05 Nov 2026 19:10:22 +0100 [thread overview]
Message-ID: <179390222262.2940962.16480771768369403374.b4-review@b4> (raw)
In-Reply-To: <20261101235155.124059-1-mirian.shilakadze@virtuozzo.com>
Applying with these fixes on my side:
- a Feature: line in every patch, "Feature: fix ms/cgroup" in patches
1-4 and 6, "Feature: fix ms/drm" in patch 5;
- patch 6: rewrote the rebase note. It now has one paragraph on what is
taken and why the old write changed nothing, one on what is left out
and why, and a per-driver list of what a lower dmem.max does now. It
also says that TTM evicts only when an allocation has no other
placement, not at every next allocation.
On Mon, 02 Nov 2026 03:51:42 +0400, Mirian Shilakadze wrote:
> Patch 6 is an adapted 747c4bb450ad: a dmem.max below the current usage
> takes effect at once, as upstream, instead of being dropped while the
> write reports success. Its reclaim callback is left out, see the rebase
> note.
Thanks. One more upstream stable fix for the same code applies here:
e773798e14ac0 ("drm/amdgpu: Fix init ordering in
amdgpu_vram_mgr_init()"). amdgpu_vram_mgr_init() registers the dmem
region before the lists and the buddy allocator are set up, so a
failed registration at probe makes amdgpu_vram_mgr_fini() walk
uninitialised lists. I created a bug for it, please send the backport
as a separate patch:
https://virtuozzo.atlassian.net/browse/VSTOR-153702
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-05 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 23:51 Mirian Shilakadze
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 1/6] ms/cgroup/dmem: fix NULL pointer dereference when setting max Mirian Shilakadze
2026-11-01 23:54 ` no-reply
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 2/6] ms/cgroup/dmem: avoid rcu warning when unregister region Mirian Shilakadze
2026-11-01 23:55 ` no-reply
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 3/6] ms/cgroup/dmem: avoid pool UAF Mirian Shilakadze
2026-11-01 23:56 ` no-reply
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 4/6] ms/cgroup/dmem: Return -ENOMEM on failed pool preallocation Mirian Shilakadze
2026-11-01 23:55 ` no-reply
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 5/6] ms/drm/ttm: Convert -EAGAIN from dmem_cgroup_try_charge to -ENOSPC Mirian Shilakadze
2026-11-01 23:56 ` no-reply
2026-11-01 23:51 ` [Devel] [PATCH hci-8.1 6/6] ms/cgroup/dmem: Add reclaim callback for lowering max below current usage Mirian Shilakadze
2026-11-01 23:57 ` no-reply
2026-11-05 17:15 ` [Devel] [PATCH hci-8.1 0/6] cgroup/dmem: backport fixes and apply a lower dmem.max at once Pavel Tikhomirov
2026-11-05 18:10 ` Konstantin Khorenko [this message]
2026-11-05 18:10 ` 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=179390222262.2940962.16480771768369403374.b4-review@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--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