https://bugs.kde.org/show_bug.cgi?id=444224
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |FIXED
CC| |m...@klomp.org
--- Comment #2 from Mark Wielaard <m...@klomp.org> ---
This was added in 3.17.0. So lets close this.
There are some followup bugs for more functionality.
e.g. Bug #439226 Multiple io_urings per thread not supported
and Bug #428364 Signals inside io_uring_enter not handled
If there are other issues please open a new bug.
commit 97fa86915e717dc68123f05b668b73adfe8885a9
Author: Bart Van Assche <bvanass...@acm.org>
Date: Mon Jul 1 15:09:04 2019 -0700
Add support for the Linux io_uring system calls
Man pages and test code are available in the following git repository:
http://git.kernel.dk/cgit/liburing/
commit b918f710208889d579026627830a80b24be1513d
Author: Mark Wielaard <m...@klomp.org>
Date: Thu Feb 4 17:21:56 2021 +0100
PR423361 Adds io_uring support on arm64/aarch64 (and all other arches)
io_uring syscalls only work on x86/amd64, but they can be enabled on
all arches. Based on a patch by Nathan Ringo <nat...@remexre.xyz>.
https://bugs.kde.org/show_bug.cgi?id=423361
commit c90561e20f7df2e9c5ae30f1cdafd330b0172345
Author: Mark Wielaard <m...@klomp.org>
Date: Wed Feb 9 23:37:53 2022 +0100
Do not try to record fd name for io_uring_setup
In POST(sys_io_uring_setup) we tried to use record_fd_open_with_given_name
with ARG1 as name. But ARG1 isn't a char pointer. So this might crash with
--track-fds=yes. Since no (file) name is associated with the fd returned by
io_uring_setup use record_fd_open_nameless instead.
https://bugs.kde.org/show_bug.cgi?id=449838
--
You are receiving this mail because:
You are watching all bug changes.
