A CT with an AIO context fails to restore on a node with more possible CPUs: io_setup() makes a bigger ring there, and CRIU needs the ring of the dumped size. Skip the CPU heuristic of the ring size while the VE is pseudosuper, and add a selftest for it.
https://virtuozzo.atlassian.net/browse/VSTOR-154129 --- Changes in v2: - fs/aio: a ring restored below the minimum of this node doesn't use the per-CPU caches of free slots. - fs/aio: say the VE is pseudosuper almost only for the restore. - selftests/ve: destroy the VE when setup fails after make_ve(), and ASSERT_EQ for set_pseudosuper(). - Link to v1: http://lore.virtuozzo.com/20261113-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-v1-0-7d35d143f...@virtuozzo.com --- Pavel Tikhomirov (2): fs/aio: restore the AIO ring of the dumped size in a pseudosuper VE selftests/ve: check the AIO ring size in a pseudosuper VE fs/aio.c | 21 ++- tools/testing/selftests/ve/.gitignore | 1 + tools/testing/selftests/ve/Makefile | 1 + tools/testing/selftests/ve/ve_aio_ring_test.c | 218 ++++++++++++++++++++++++++ 4 files changed, 240 insertions(+), 1 deletion(-) --- base-commit: 3874c7f41089f93b796592c13b410ded6c987ec8 change-id: 20261113-pr-ptikhomirov-vstor-154129-aio-pseudosuper-ring-ae2133423a88 Best regards, -- Pavel Tikhomirov <[email protected]> _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
