diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2024-02-02 10:45:17 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2024-02-02 10:45:17 -0800 |
commit | 717ca0b8e55eea49c5d71c026eafbe1e64d4b556 (patch) | |
tree | 40889fa3e19f9626e5fe9184abef01ec3163ebb8 /include | |
parent | ec86369c88f6794a6cfa0383f715f276305399ed (diff) | |
parent | 72bd80252feeb3bef8724230ee15d9f7ab541c6e (diff) |
Merge tag 'io_uring-6.8-2024-02-01' of git://git.kernel.dk/linux
Pull io_uring fixes from Jens Axboe:
- Fix for missing retry for read multishot.
If we trigger the execution of it and there's more than one buffer to
be read, then we don't always read more than the first one. As it's
edge triggered, this can lead to stalls.
- Limit inline receive multishot retries for fairness reasons.
If we have a very bursty socket receiving data, we still need to
ensure we process other requests as well. This is really two minor
cleanups, then adding a way for poll reissue to trigger a requeue,
and then finally having multishot receive utilize that.
- Fix for a weird corner case for non-multishot receive with
MSG_WAITALL, using provided buffers, and setting the length to
zero (to let the buffer dictate the receive size).
* tag 'io_uring-6.8-2024-02-01' of git://git.kernel.dk/linux:
io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers
io_uring/net: limit inline multishot retries
io_uring/poll: add requeue return code from poll multishot handling
io_uring/net: un-indent mshot retry path in io_recv_finish()
io_uring/poll: move poll execution helpers higher up
io_uring/rw: ensure poll based multishot read retries appropriately
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions