# io_uring: don't assume completions order \(2\) · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/b8890f8ee1cb36e425afd96c0058fc382eb7cf39)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: b8890f8ee1cb36e425afd96c0058fc382eb7cf39

Requested commit: b8890f8ee1cb36e425afd96c0058fc382eb7cf39

Commit: b8890f8ee1cb36e425afd96c0058fc382eb7cf39

Tree: 2f466ca56c6322dad34252fdeec0046428169786

Author: Igor Anić

Committer: Andrew Kelley

## Message

```
io_uring: don't assume completions order (2)

In my first [try](https://github.com/ziglang/zig/pull/20224) to fix
20212 I didn't reproduce bug on required kernel (6.9.2) and wrongly
concluded that first two completions have different order on newer
kernel.
On my current kernel (6.5.0) order of completions is: send1, recv,
send2. On 6.9.2 order is send1, send2, recv. This fix allows second two
completions to arrive in any order.
Tested on both kernels.

Fixes: #20212

```

## Parents

- [e03026507f6e3f0b60947d9859c1346f64f480b6](https://git.cafe/gitcafe/zig/commit/e03026507f6e3f0b60947d9859c1346f64f480b6?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/b8890f8ee1cb36e425afd96c0058fc382eb7cf39?format=markdown)