aboutsummaryrefslogtreecommitdiff
path: root/src/codegen
diff options
context:
space:
mode:
authorVincent Rischmann <vincent@rischmann.fr>2022-07-16 17:05:11 +0200
committerGitHub <noreply@github.com>2022-07-16 10:05:11 -0500
commit47c58cba595a8e1eddf6c87086d52691d180a103 (patch)
tree84ed8e541eaf92bf1d98d5849e89203fa0cf6974 /src/codegen
parent9c66fdadc709ca4c00b08aa8fa4dc6312cb559c3 (diff)
downloadzig-47c58cba595a8e1eddf6c87086d52691d180a103.tar.gz
zig-47c58cba595a8e1eddf6c87086d52691d180a103.zip
Fix io_uring tests (#12134)
* io_uring: fix the timeout_remove test The test does a IORING_OP_TIMEOUT followed with a IORING_OP_TIMEOUT_REMOVE and assumed we would get the CQEs in the same order. Linux v5.18 changed how this works and we now get them in the reverse order. The documentation doesn't explicitly say which CQE we should get first so just make the test work with both cases. * io_uring: fix the remove_buffers test The original test was buggy but accidentally worked with kernels < 5.18 The test assumed that IORING_OP_REMOVE_BUFFERS removed from the start of but in fact the documentation doesn't specify which buffer is removed, only that a certain number of buffers are removed. Starting with the kernel 5.18 the check for the `used_buffer_id` fails. Turns out that previous kernels removed buffers in such a way that the remaining buffer for this read would always be 0, however this isn't true anymore. Instead of checking a specific value just check that the `used_buffer_id` corresponds to a valid ID.
Diffstat (limited to 'src/codegen')
0 files changed, 0 insertions, 0 deletions