What impact does disabling of io_uring have on KDE

In the kernel the io_uring is a interface for asynchronous I/O operations for storage devices. It is supposed to be the fastest one out there in terms of asynchronous I/O calls. But it has its own fair share of security vulunerabilities to go along with it. For example Google Vulnerability Rewards Program for Linux kernel had listed io_uring is one of the most effective way for an unprivileged process to gain access to kernel.
Disabling it is easy, with its impact on Samba Servers, NFS servers, a few databases (MariaDB/PostgreSQL), a few emulators and vms being known.

When I looked at the dependencies on a KDE EOS desktop, I realized KDE qt6-base is dependent on the liburing. liburing is the Linux-native io_uring I/O access library. This dependency on liburing is not an optional but a hard one, required.

So my question, if io_uring is disabled by setting the kernel parameter kernel.io_uring_disabled then does it impact severely the working of KDE Plasma desktop? Will the KDE instance become comatose or only glacial/slow? What will be the adverse impact on day-to-day working of KDE desktop?

I don’t know, and nobody here will know. Your only option is to try it and have a live media available to use as recovery. There may be plagues of frogs and locusts. :cricket: