Our great sponsors
-
-
Has this problem been filed as an issue with Jens Axboe? I would like to hear his response to it. https://github.com/axboe/liburing I believe.
> There's also alot of security implications
To be clear, this is liburing, NOT the io_uring syscalls that I would assume Tokio would opt for.
> io_uring is basically just a threaded work dispatcher
Only under SQPOLL mode. This isn't an inherent property of io_uring.
> All these process semantics are totally hidden and non-obvious
Again, only if you use liburing. The syscalls make this abundantly clear, as there's no other way to program for them.
> These known and unknown future pitfalls
The problem isn't with io_uring here, the problem is with the over-saturation of the development world with people who do not care about doing things correctly or safely but instead quickly and cost-effectively.
This is not unique to io_uring, however. Let's not throw the baby out with the bathwater.
> And all the fanciest programming language type safety in the world won't save you.
I agree whole-heartedly.
> Expect several years of easy remote exploits down the road...
I would rather be interested to see which sidechannels were attacked in order to take advantage of io_uring. Those vulns are going to lay with the framework implementors and the users of frameworks, less with io_uring. But I understand the concern.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
