From: no-reply@sashiko.virtuozzo.com
To: khorenko@virtuozzo.com, Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2] ve: start the kthreads of a container in its ve namespace
Date: Tue, 3 Nov 2026 17:47:18 +0000 [thread overview]
Message-ID: <010701a1a285c57a-9ecf0c98-7822-47c0-bef0-db297b1c6e62-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261103173909.2589573-1-eva.kurchatova@virtuozzo.com>
> The kthreadd of a container is forked from a worker that takes over the
> namespaces, root, credentials and cgroups of the task starting the
> container, but not its ve namespace, which is not part of nsproxy.
>
> As task_ve follows the ve namespace, they all run as host tasks, and so
> do the usermode helpers they start, and so a core dump to a pipe in a
> container fails, since the host won't execute a file from an untrusted
> container disk.
>
> Switch the worker into the ve namespace of the starting task as well,
> last, as setns() does.
>
> Fixes: 4d033dd01fd3 ("ve: Make task_ve pointer ve namespace based")
> https://virtuozzo.atlassian.net/browse/VSTOR-152982
> Feature: ve: ve generic structures
>
> Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261103173909.2589573-1-eva.kurchatova@virtuozzo.com?part=1
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-03 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 17:37 Eva Kurchatova
2026-11-03 17:47 ` no-reply [this message]
2026-11-03 18:18 ` 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=010701a1a285c57a-9ecf0c98-7822-47c0-bef0-db297b1c6e62-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
--cc=khorenko@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.