Allow cancelation based on fd
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | io_uring: remove dead 'poll_only' argument to io_poll_cancel()fs/ | +3 | 0 replies | |
| 2/4 | io_uring: pass in struct io_cancel_data consistentlyfs/ | +29 | 0 replies | |
| 3/4 | io_uring: rename io_cancel_data->user_data to just 'data'fs/ | +8 | 0 replies | |
| 4/4 | io_uring: allow IORING_OP_ASYNC_CANCEL with 'fd' keyfs/ include/ | +56 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCHSET next 0/4] Allow cancelation based on fd
Hi,
We currently only support looking up and canceling requests based on the user_data of the original request. Sometimes it can be useful to instead key off the fd used in the original request, eg if a socket goes away.
Patch 1 is just a cleanup spotted while doing this, 2+3 are prep patches, and patch 4 then finally is the meat of it.
Adds IORING_ASYNC_CANCEL_FD as a IORING_OP_ASYNC_CANCEL request flag, which tells the kernel that we're looking up by fd rather than user_data.
Signature · 1 line
Jens Axboe