summaryrefslogtreecommitdiff
path: root/Documentation/process/maintainers.rst
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2024-02-14 18:23:05 +0300
committerJens Axboe <axboe@kernel.dk>2024-02-15 04:30:19 +0300
commita37ee9e117ef73bbc2f5c0b31911afd52d229861 (patch)
treeae2d6b3224b9e5e8d4a9d967a1d7f1b8afcb57b9 /Documentation/process/maintainers.rst
parent72bd80252feeb3bef8724230ee15d9f7ab541c6e (diff)
downloadlinux-a37ee9e117ef73bbc2f5c0b31911afd52d229861.tar.xz
io_uring/net: fix multishot accept overflow handling
If we hit CQ ring overflow when attempting to post a multishot accept completion, we don't properly save the result or return code. This results in losing the accepted fd value. Instead, we return the result from the poll operation that triggered the accept retry. This is generally POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND which is 0xc3, or 195, which looks like a valid file descriptor, but it really has no connection to that. Handle this like we do for other multishot completions - assign the result, and return IOU_STOP_MULTISHOT to cancel any further completions from this request when overflow is hit. This preserves the result, as we should, and tells the application that the request needs to be re-armed. Cc: stable@vger.kernel.org Fixes: 515e26961295 ("io_uring: revert "io_uring fix multishot accept ordering"") Link: https://github.com/axboe/liburing/issues/1062 Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'Documentation/process/maintainers.rst')
0 files changed, 0 insertions, 0 deletions