OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: Vladimir Riabchun <vladimir.riabchun@virtuozzo.com>
To: devel@openvz.org
Subject: [Devel] [PATCH VZ10 v8 0/7] Add per-VE failcount support
Date: Wed,  9 Sep 2026 21:35:22 +0000	[thread overview]
Message-ID: <cover.1788989664.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.
- Patches 2-4 change mount number and limit processing,
  unifying it with other resources. VE selftest is updated
  in patch 3.
- Patch 5 greatly reduces the amount of copy-pasted code
  by introducing some useful macros.
- Patch 6 adds per-VE failcount file.
- Patch 7 introduces new VE selftest, that checks mounts
  accounting, limits and failcount updates.

NOTE: for running new selftest this change should be applied on
top of "[PATCH VZ10 v2 0/3] Improvements for ve selftests" patchset.

https://virtuozzo.atlassian.net/browse/VSTOR-135520

Changes since v7:
 - Rebased on h10-6.12.0-211.52.1.20.x.vz10-ovz
 - After rebase old patch 2 has gone.
 - Reworked mount count covered ve_mount_reown after rebase.
 - Failcount patch now has fancy ve_failcount_inc macro that
   prints error report to both CT and host dmesg.
 - Selftest harness improvements were moved to a separate
   change. Only new selftest was left.
 - The selftest was completely reworked - some copy-paste dropped,
   number tracking changed due to fixed mount ownership.

Vladimir Riabchun (7):
  ve/ve.{h,c}: Farewell to spaces as indents
  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 mount accounting selftest

 fs/aio.c                                      |   1 +
 fs/namespace.c                                |  80 +--
 include/linux/ve.h                            |  35 +-
 kernel/bpf/syscall.c                          |   1 +
 kernel/ve/ve.c                                | 277 +++++-----
 kernel/ve/veowner.c                           |  19 -
 net/core/dev.c                                |  10 +-
 net/core/neighbour.c                          |   3 +-
 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   | 489 ++++++++++++++++++
 tools/testing/selftests/ve/ve_ns_owner_test.c |  37 +-
 13 files changed, 736 insertions(+), 222 deletions(-)
 create mode 100644 tools/testing/selftests/ve/ve_mount_accounting_test.c

-- 
2.47.1

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

             reply	other threads:[~2026-09-09 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 21:35 Vladimir Riabchun [this message]
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 1/7] ve/ve.{h, c}: Farewell to spaces as indents Vladimir Riabchun
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 2/7] ve/fs: Rework per-ve mount count Vladimir Riabchun
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 3/7] selftests/ve: Update ve_ns_owner_test Vladimir Riabchun
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 4/7] ve: Move from global VE mounts limit to per-VE limit Vladimir Riabchun
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 5/7] ve/ve.c: Generate VE resource accessors using macros Vladimir Riabchun
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 6/7] ve: Introduce per-VE failcount Vladimir Riabchun
2026-09-14  9:35   ` Vasileios Almpanis
2026-09-09 21:35 ` [Devel] [PATCH VZ10 v8 7/7] selftests/ve: Add mount accounting selftest Vladimir Riabchun
2026-09-14  9:35   ` 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=cover.1788989664.git.vladimir.riabchun@virtuozzo.com \
    --to=vladimir.riabchun@virtuozzo.com \
    --cc=devel@openvz.org \
    /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