71–79 of 79 posts
Earlier quoted context omitted.
What's the singular function that has a chance of turning out to be exploitable in the future?
With seccomp you can disable a single syscall which might be exploitable since you didn’t get around to patch your kernel, with cBPF you can now do the same for io_uring
Earlier quoted context omitted.
With seccomp you can disable a single syscall which might be exploitable since you didn’t get around to patch your kernel, with cBPF you can now do the same for io_uring
And which single syscall might be exploitable? I don't wanna wait until after an exploit to disable it
Earlier quoted context omitted.
And which single syscall might be exploitable? I don't wanna wait until after an exploit to disable it
Nothing stops you from disabling everything you don’t need and now io_uring offers that per OP too.
Earlier quoted context omitted.
And which single syscall might be exploitable? I don't wanna wait until after an exploit to disable it
Nothing stops you from disabling everything you don’t need and now io_uring offers that per OP too.
Gotta read the usual sources to find out what you gotta disable on your machines, like you have to for every single syscall since forever.
Earlier quoted context omitted.
Nothing stops you from disabling everything you don’t need and now io_uring offers that per OP too.
I don’t get what you mean, in the past it was all or nothing, now you can disable every single operation selectively. Gotta read the usual sources to find out what you gotta disable on your machines, like you have to for every single syscall since forever.
Just use AF_XDP
Just use AF_XDP
That only applies for network sockets, and requires taking responsibility for the entire network protocol stack. Not something that should be done without a very compelling reason, and not applicable at all in this case, where storage devices are involved.
Such a great article! This sent me through a rabbit hole of uring, kernel development and C. I've been a rust and c++ dev for quite a few years now, but there's such a simplicity and even artistic feel to small(ish) C programs.
https://unixism.net/loti/index.html
Feel free to reverse-search the related HN thread too.
Such a great article! This sent me through a rabbit hole of uring, kernel development and C. I've been a rust and c++ dev for quite a few years now, but there's such a simplicity and even artistic feel to small(ish) C programs.
This article is very brief and not deep enough. There is one I’m finding a much more “to the bone” and explaining io_uring concepts in much deeper details: https://unixism.net/loti/index.html Feel free to reverse-search the related HN thread too.