From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>,
Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 0/2] ve/fs: allow host to go over container mount limit
Date: Mon, 28 Sep 2026 17:24:56 +0200 [thread overview]
Message-ID: <20260928-b4-ve0-mnt-limit-v1-0-66456b9eaf6f@virtuozzo.com> (raw)
Since 22.4 CRIU fails to dump a container which is close to its mount
limit:
Error (criu/mount.c:1740): mnt: Unable to unshare a mount namespace: Cannot allocate memory
To get access to overmounted mounts, CRIU (in ve0) copies the container
mount namespace. The copied mounts are owned by and charged to the
container, and now the container limit is also checked for them, so the
host is restricted by the container limit.
Patch 1 relaxes the limit for ve0 (still counting, as for pseudosuper),
patch 2 adds a selftest for it.
https://virtuozzo.atlassian.net/browse/VSTOR-147661
Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
---
Pavel Tikhomirov (2):
ve/fs: allow host to go over limit of container mount namespace
selftests/ve: check that host can go over container mount limit
fs/namespace.c | 3 +-
.../selftests/ve/ve_mount_accounting_test.c | 37 ++++++++++++++++++++++
2 files changed, 39 insertions(+), 1 deletion(-)
---
base-commit: ca54f152160587a74ff17cb52feef16f7b9d4e2b
change-id: 20260928-b4-ve0-mnt-limit-5bdc176203a4
Best regards,
--
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-09-28 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 15:24 Pavel Tikhomirov [this message]
2026-09-28 15:24 ` [Devel] [PATCH hci-8.1 1/2] ve/fs: allow host to go over limit of container mount namespace Pavel Tikhomirov
2026-09-28 15:24 ` [Devel] [PATCH hci-8.1 2/2] selftests/ve: check that host can go over container mount limit Pavel Tikhomirov
2026-09-30 15:05 ` [Devel] [PATCH hci-8.1 0/2] ve/fs: allow host to " Konstantin Khorenko
2026-09-30 15:09 ` 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=20260928-b4-ve0-mnt-limit-v1-0-66456b9eaf6f@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=vasileios.almpanis@virtuozzo.com \
--cc=vladimir.riabchun@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.