aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/rl-next/block-io-uring.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual/rl-next/block-io-uring.md')
-rw-r--r--doc/manual/rl-next/block-io-uring.md12
1 files changed, 0 insertions, 12 deletions
diff --git a/doc/manual/rl-next/block-io-uring.md b/doc/manual/rl-next/block-io-uring.md
deleted file mode 100644
index 6ebba9a20..000000000
--- a/doc/manual/rl-next/block-io-uring.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-synopsis: "Block io_uring in the Linux sandbox"
-cls: 1611
-credits: alois31
-category: Breaking Changes
----
-
-The io\_uring API has the unfortunate property that it is not possible to selectively decide which operations should be allowed.
-This, together with the fact that new operations are routinely added, makes it a hazard to the proper function of the sandbox.
-
-Therefore, any access to io\_uring has been made unavailable inside the sandbox.
-As such, attempts to execute any system calls forming part of this API will fail with the error `ENOSYS`, as if io\_uring support had not been configured into the kernel.