diff options
| author | Jens Axboe <[email protected]> | 2024-09-20 08:51:20 +0000 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2024-09-20 08:51:20 +0000 |
| commit | eac2ca2d682f94f46b1973bdf5e77d85d77b8e53 (patch) | |
| tree | 6be423321fe1600de73a2220d13499679b64474a /rust/helpers | |
| parent | io_uring: improve request linking trace (diff) | |
| download | kernel-eac2ca2d682f94f46b1973bdf5e77d85d77b8e53.tar.gz kernel-eac2ca2d682f94f46b1973bdf5e77d85d77b8e53.zip | |
io_uring: check if we need to reschedule during overflow flush
In terms of normal application usage, this list will always be empty.
And if an application does overflow a bit, it'll have a few entries.
However, nothing obviously prevents syzbot from running a test case
that generates a ton of overflow entries, and then flushing them can
take quite a while.
Check for needing to reschedule while flushing, and drop our locks and
do so if necessary. There's no state to maintain here as overflows
always prune from head-of-list, hence it's fine to drop and reacquire
the locks at the end of the loop.
Link: https://lore.kernel.org/io-uring/[email protected]/
Reported-by: [email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'rust/helpers')
0 files changed, 0 insertions, 0 deletions
