From: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
To: Konstantin Khorenko <khorenko@virtuozzo.com>,
vasileios.almpanis@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH VZ10 v3 0/3] Improvements for ve selftests
Date: Wed, 09 Sep 2026 21:32:47 +0000 [thread overview]
Message-ID: <20260909-ve-selftest-improv-v3-0-4b41980d9a45@virtuozzo.com> (raw)
This change adds helpers for creating and preserving various
namespaces and running functions inside them.
This appeared useful while implementing ve mount accounting
selftests - it required keeping mount namespace alive and
doing different things at different moments of time.
To make setns work with CLONE_NEWVE without starting VE,
the last patch changes -EINVAL return to warning message.
https://virtuozzo.atlassian.net/browse/VSTOR-144504
Feature: ve selftests
Signed-off-by: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
---
Changes in v3:
- Patch 1: wrap flag -> (flag) in macros, undef them after use.
- Patch 2: Fix comments in run_in_ve function.
- Link to v2: http://lore.virtuozzo.com/20260909-ve-selftest-improv-v2-0-aad0a25d6569@virtuozzo.com
Changes in v2:
- Patch 1: fixed JOIN_NS order in enter_namespaces, added proper
cleanup in prepare_namespaces.
- Patch 2: increased buf size in write_u64_at, added range check in
read_s32_at, separated setup failures in run_in_ve from fn setup
failures.
- Patch 3: Removed kselftests mention.
- Sashiko review: https://sashiko.vzint.dev/#/patchset/sashiko-inject-1788867622-560139540%40sashiko.local
- Link to v1: http://lore.virtuozzo.com/20260907-ve-selftest-improv-v1-0-a17847abbd48@virtuozzo.com
---
Vladimir Riabchun (3):
selftests/ve: Add namespace management helpers
selftests/ve: Add more helpers
ve_namespace: Allow entering non-running VE namespace
kernel/ve/ve_namespace.c | 3 +-
tools/testing/selftests/ve/ve_selftest.h | 211 ++++++++++++++++++++++++++++++-
2 files changed, 206 insertions(+), 8 deletions(-)
---
base-commit: 04cfdce5ceb48a93de722643c2afe8065ca8fc10
change-id: 20260907-ve-selftest-improv-2d043d021cae
Best regards,
--
Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-09-09 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 21:32 Vladimir Riabchun [this message]
2026-09-09 21:32 ` [Devel] [PATCH VZ10 v3 1/3] selftests/ve: Add namespace management helpers Vladimir Riabchun
2026-09-09 21:32 ` [Devel] [PATCH VZ10 v3 2/3] selftests/ve: Add more helpers Vladimir Riabchun
2026-09-09 21:32 ` [Devel] [PATCH VZ10 v3 3/3] ve_namespace: Allow entering non-running VE namespace Vladimir Riabchun
2026-09-15 12:28 ` [Devel] [PATCH VZ10 v3 0/3] Improvements for ve selftests Vasileios Almpanis
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=20260909-ve-selftest-improv-v3-0-4b41980d9a45@virtuozzo.com \
--to=vladimir.riabchun@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@virtuozzo.com \
--cc=vasileios.almpanis@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