From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: ptikhomirov@virtuozzo.com,
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:35 +0100 [thread overview]
Message-ID: <179390223534.2940962.4203647602891220323.b4-ty@b4> (raw)
In-Reply-To: <20261101235155.124059-1-mirian.shilakadze@virtuozzo.com>
On Mon, 02 Nov 2026 03:51:42 +0400, Mirian Shilakadze wrote:
> cgroup/dmem: backport fixes and apply a lower dmem.max at once
>
> Per-container GPU memory limits (VSTOR-135023) enable the dmem cgroup
> controller for Containers. Our dmem.c is upstream as of 8821f36333e2
> (6.14) and lacks four upstream fixes tagged for stable. The first one
> matters most: with dmem enabled for Containers, root in a Container can
> write a region name without a value to dmem.max of its own child
> cgroup, which dereferences NULL and, with CONFIG_PANIC_ON_OOPS=y,
> panics the node.
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.19.vz10, thanks!
[1/6] ms/cgroup/dmem: fix NULL pointer dereference when setting max
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/0200fe88bdaf
[2/6] ms/cgroup/dmem: avoid rcu warning when unregister region
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/9b121ec55c44
[3/6] ms/cgroup/dmem: avoid pool UAF
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/ee01dba6198e
[4/6] ms/cgroup/dmem: Return -ENOMEM on failed pool preallocation
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/667e36696982
[5/6] ms/drm/ttm: Convert -EAGAIN from dmem_cgroup_try_charge to -ENOSPC
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d332229c6025
[6/6] ms/cgroup/dmem: Add reclaim callback for lowering max below current usage
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/b0077f5fcb71
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
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
2026-11-05 18:10 ` Konstantin Khorenko [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=179390223534.2940962.4203647602891220323.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=mirian.shilakadze@virtuozzo.com \
--cc=ptikhomirov@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