From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>,
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/2] ve/fs: allow host to go over container mount limit
Date: Wed, 30 Sep 2026 17:09:50 +0200 [thread overview]
Message-ID: <179078099011.3608222.10836887226853338237.b4-ty@b4> (raw)
In-Reply-To: <20260928-b4-ve0-mnt-limit-v1-0-66456b9eaf6f@virtuozzo.com>
On Mon, 28 Sep 2026 17:24:56 +0200, Pavel Tikhomirov wrote:
> ve/fs: allow host to go over container mount limit
>
> 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
>
> [...]
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.5.vz10, thanks!
[1/2] ve/fs: allow host to go over limit of container mount namespace
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/e6358d78bde7
[2/2] selftests/ve: check that host can go over container mount limit
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/95abfad2aff6
--
Konstantin Khorenko <khorenko@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-09-30 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 15:24 Pavel Tikhomirov
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 [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=179078099011.3608222.10836887226853338237.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=ptikhomirov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox