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 and 4 change mount number and limit processing, unifying it with other resources. - Patch 5 greatly reduces the amount of copy-pasted code by introducing some useful macros. - Patch 6 adds per-VE failcount file. Side note: it may worth reworking AIO accounting as well, now it is a bit ugly with a spinlock. https://virtuozzo.atlassian.net/browse/VSTOR-135520 Changes since v1: - Rebase to rh10-6.12.0-211.30.1.14.x.vz10-ovz - Fix issues in patch 3 by passing ve value to ve_mount_put helper and removing is_pseudosuper check. Vladimir Riabchun (6): ve/ve.{h,c}: Farewell to spaces as indents ve/namespace: Fix UAF in alloc_mnt_ns ve/fs: Rework per-ve mount count 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 fs/aio.c | 1 + fs/namespace.c | 75 ++--- include/linux/ve.h | 23 +- kernel/bpf/syscall.c | 1 + kernel/ve/ve.c | 276 +++++++++--------- 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/ve_ns_owner_test.c | 33 ++- 10 files changed, 223 insertions(+), 212 deletions(-) -- 2.47.1 _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
