> Linux’s io_uring is a relatively recent addition that improves asynchronous I/O, but it has been a significant source of security vulnerabilities and is not in widespread use.
Funny, opening the manpage of aio on freebsd you get this on the second paragraph
> Asynchronous I/O operations on some file descriptor types may block an
> AIO daemon indefinitely resulting in process and/or system hangs.
> Operations on these file descriptor types are considered “unsafe” and
> disabled by default. They can be enabled by setting the
> vfs.aio.enable_unsafe sysctl node to a non-zero value.
those are unsafe from different perspectives - AFAIR, io_uring just passed some/many filtering mechanics applied to other subsystems in kernel when say reading/writing files, so security frameworks could not be enforced. Something about auditd subsystem as well.
Funny, opening the manpage of aio on freebsd you get this on the second paragraph
> Asynchronous I/O operations on some file descriptor types may block an > AIO daemon indefinitely resulting in process and/or system hangs. > Operations on these file descriptor types are considered “unsafe” and > disabled by default. They can be enabled by setting the > vfs.aio.enable_unsafe sysctl node to a non-zero value.
So nothing is safe.