From: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
Subject: [Devel] [PATCH VZ10 v7 0/9] Add per-VE failcount support
Date: Mon, 24 Aug 2026 13:54:42 +0000 [thread overview]
Message-ID: <cover.1787579160.git.vladimir.riabchun@virtuozzo.com> (raw)
This patchset introduces per-VE failcount support.
We have several resources, that have per-VE limits,
the users might want to know what limit hits make
operations fail.
- Patch 1 is cosmetic, nothing special.
- Patch 2 is a bugfix, found when testing per-VE mount
limits (but now comes before these changes).
- Patches 3-5 change mount number and limit processing,
unifying it with other resources. VE selftest is updated
in patch 4.
- Patch 6 greatly reduces the amount of copy-pasted code
by introducing some useful macros.
- Patch 7 adds per-VE failcount file.
- Patch 8 adds new helpers to our VE selftests infra.
- Patch 9 introduces new VE selftest, that checks mounts
accounting, limits and failcount updates.
https://virtuozzo.atlassian.net/browse/VSTOR-135520
Changes since v6:
- Fixed several typos and adjusted comments.
- Added CONFIG_VE check in free_vfsmnt to compile with
!CONFIG_VE in patch 3.
- Added permission check in ve_failcount_write in patch 7.
Vladimir Riabchun (9):
ve/ve.{h,c}: Farewell to spaces as indents
ve/namespace: Fix UAF in alloc_mnt_ns
ve/fs: Rework per-ve mount count
selftests/ve: Update ve_ns_owner_test
ve: Move from global VE mounts limit to per-VE limit
ve/ve.c: Generate VE resource accessors using macros
ve: Introduce per-VE failcount
selftests/ve: Add more helpers
selftests/ve: Add mount accounting selftest
fs/aio.c | 1 +
fs/namespace.c | 90 ++--
include/linux/ve.h | 25 +-
kernel/bpf/syscall.c | 1 +
kernel/ve/ve.c | 277 ++++++------
kernel/ve/veowner.c | 19 -
net/core/dev.c | 2 +
net/core/neighbour.c | 1 +
net/core/net_namespace.c | 4 +-
tools/testing/selftests/ve/.gitignore | 1 +
tools/testing/selftests/ve/Makefile | 1 +
.../selftests/ve/ve_mount_accounting_test.c | 421 ++++++++++++++++++
tools/testing/selftests/ve/ve_ns_owner_test.c | 37 +-
tools/testing/selftests/ve/ve_selftest.h | 81 +++-
14 files changed, 740 insertions(+), 221 deletions(-)
create mode 100644 tools/testing/selftests/ve/ve_mount_accounting_test.c
--
2.47.1
next reply other threads:[~2026-08-24 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 13:54 Vladimir Riabchun [this message]
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 1/9] ve/ve.{h, c}: Farewell to spaces as indents Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 2/9] ve/namespace: Fix UAF in alloc_mnt_ns Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 3/9] ve/fs: Rework per-ve mount count Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 4/9] selftests/ve: Update ve_ns_owner_test Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 5/9] ve: Move from global VE mounts limit to per-VE limit Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 6/9] ve/ve.c: Generate VE resource accessors using macros Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 7/9] ve: Introduce per-VE failcount Vladimir Riabchun
2026-08-28 16:52 ` Pavel Tikhomirov
2026-08-28 17:32 ` Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 8/9] selftests/ve: Add more helpers Vladimir Riabchun
2026-08-24 13:54 ` [Devel] [PATCH VZ10 v7 9/9] selftests/ve: Add mount accounting selftest 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=cover.1787579160.git.vladimir.riabchun@virtuozzo.com \
--to=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.