From: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
To: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH VZ10 v2 1/3] selftests/ve: Add namespace management helpers
Date: Wed, 09 Sep 2026 14:33:53 +0000 [thread overview]
Message-ID: <178896443372.479408.12169265905688190706.b4-review@b4> (raw)
In-Reply-To: <20260909-ve-selftest-improv-v2-1-aad0a25d6569@virtuozzo.com>
> When mount namespace is created in a child, it is destroyed
> when the child dies. We may need to keep it for a while to check
> how VE handles resources.
>
> Instead of keeping a thread which lives in a new ve+mnt namespaces,
> let's store open namespace file descriptors to enter them later
> without keeping children alive.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-144504
>
> Feature: ve selftests
> Signed-off-by: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
>
> diff --git a/tools/testing/selftests/ve/ve_selftest.h b/tools/testing/selftests/ve/ve_selftest.h
> index c53bf7900d20..ee960f7db0b4 100644
> --- a/tools/testing/selftests/ve/ve_selftest.h
> +++ b/tools/testing/selftests/ve/ve_selftest.h
> @@ -31,6 +31,129 @@
> #define VE_CONTROLLERS \
> "+cpuset +cpu +cpuacct +io +memory +hugetlb +pids +rdma +misc +ve"
>
> +struct namespace_ctx {
> + int ns_save_mask; /* Mask of stored CLONE_NEW* namespaces. */
> + /* Namespace file descriptors. Name should match /proc/PID/ns/NAME */
> + int ve_fd;
> + int mnt_fd;
> +};
> +
> +static inline void close_namespace_fds(struct namespace_ctx *ctx)
> +{
> + if (ctx->ns_save_mask & CLONE_NEWVE)
> + close(ctx->ve_fd);
> + if (ctx->ns_save_mask & CLONE_NEWNS)
> + close(ctx->mnt_fd);
> +
> + ctx->ns_save_mask = 0;
> +}
> +
> +static inline int save_namespace_fds(struct namespace_ctx *ctx, int flags)
> +{
> +#define OPEN_NS(name, flag) \
> +do { \
> + if (flags & flag) { \
Parenthesise the macro argument, checkpatch complaints about it
if (flags & (flag))
> + ctx->name##_fd = open("/proc/self/ns/" #name, O_RDONLY); \
> + if (ctx->name##_fd < 0) { \
> + fprintf(stderr, "%s: could not open fd %s: %s\n", \
> + __func__, #name, strerror(errno)); \
> + goto err; \
> + } \
> + ctx->ns_save_mask |= flag; \
> + } \
> +} while (0)
> +
> + ctx->ns_save_mask = 0;
> +
> + OPEN_NS(ve, CLONE_NEWVE);
> + OPEN_NS(mnt, CLONE_NEWNS);
Add #undef OPEN_NS after the last call to not leak to all includers and
the same for JOIN_NS.
--
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-09-09 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:14 [Devel] [PATCH VZ10 v2 0/3] Improvements for ve selftests Vladimir Riabchun
2026-09-09 12:14 ` [Devel] [PATCH VZ10 v2 1/3] selftests/ve: Add namespace management helpers Vladimir Riabchun
2026-09-09 14:33 ` Vasileios Almpanis [this message]
2026-09-09 12:14 ` [Devel] [PATCH VZ10 v2 2/3] selftests/ve: Add more helpers Vladimir Riabchun
2026-09-09 14:33 ` Vasileios Almpanis
2026-09-09 12:14 ` [Devel] [PATCH VZ10 v2 3/3] ve_namespace: Allow entering non-running VE namespace Vladimir Riabchun
2026-09-09 14:33 ` Vasileios Almpanis
2026-09-09 18:56 ` Vladimir Riabchun
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=178896443372.479408.12169265905688190706.b4-review@b4 \
--to=vasileios.almpanis@virtuozzo.com \
--cc=devel@openvz.org \
--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