instead of this patch and the next one i have committed a merged one
+ i have switched from handling old_io_uring_disabled as a string to handling it as int and
write/restore only in case the values != 0 already.
If any objections, please let me know.
--
Best regards,
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
On 12/23/25 23:22, Aleksei Oladko wrote:
The io_uring_zerocopy.sh kselftest assumes that io_uring support is
enabled on the host system. When io_uring is disabled via the
kernel.io_uring_disabled sysctl, the test fails.
Explicitly enable io_uring for the test by setting
kernel.io_uring_disabled=0
https://virtuozzo.atlassian.net/browse/VSTOR-120995
Signed-off-by: Aleksei Oladko <[email protected]>
---
tools/testing/selftests/net/io_uring_zerocopy_tx.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/net/io_uring_zerocopy_tx.sh
b/tools/testing/selftests/net/io_uring_zerocopy_tx.sh
index 123439545013..1b0816760534 100755
--- a/tools/testing/selftests/net/io_uring_zerocopy_tx.sh
+++ b/tools/testing/selftests/net/io_uring_zerocopy_tx.sh
@@ -122,5 +122,7 @@ do_test() {
wait
}
+sysctl -w -q kernel.io_uring_disabled=0
+
do_test "${EXTRA_ARGS}"
echo ok
_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel
