| Summary: | Add new io_uring_register, setup, enter syscalls | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | zbbjornson |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | boxerab, mark, xonatius, zbbjornson |
| Priority: | NOR | ||
| Version First Reported In: | 3.15 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
zbbjornson
2019-06-18 02:49:56 UTC
Do you have a patch that fixes this, or any test cases? I don't have a usable patch unfortunately. (Have a sloppy one that I could try to rework sometime.) The easiest test is probably the liburing test suite: https://github.com/axboe/liburing or fio with ioengine=io_uring: https://github.com/axboe/fio (In reply to zbbjornson from comment #2) > I don't have a usable patch unfortunately. (Have a sloppy one that I could > try to rework sometime.) Feel free to post your "sloppy" patch. It could help someone come up with a full/real one. LWN has some more background on io_uring: https://lwn.net/Kernel/Index/#io_uring *** Bug 428858 has been marked as a duplicate of this bug. *** Looks like the new syscalls were added in https://sourceware.org/git/?p=valgrind.git;a=commit;h=97fa86915e717dc68123f05b668b73adfe8885a9 This commit, however, was added after 3.15 version, but it should be fixed in 3.16. |