| commit | f010505b78a4fa8d5b6480752566e7313fb5ca6e | |
| author | Marcelo Diop-Gonzalez <marcelo827@gmail.com> | |
| Fri, 15 Jan 2021 16:54:40 +0000 (15 11:54 -0500) | ||
| committer | Jens Axboe <axboe@kernel.dk> | |
| Fri, 15 Jan 2021 17:02:28 +0000 (15 10:02 -0700) | ||
| tree | e441b11c2ebe22618a96bb6db65ff88d66fb5753 | treesnapshot (tar.gz zip) |
| parent | 06585c497b55045ec21aa8128e340f6a6587351c | commitdiff |
io_uring: flush timeouts that should already have expired
Right now io_flush_timeouts() checks if the current number of events
is equal to ->timeout.target_seq, but this will miss some timeouts if
there have been more than 1 event added since the last time they were
flushed (possible in io_submit_flush_completions(), for example). Fix
it by recording the last sequence at which timeouts were flushed so
that the number of events seen can be compared to the number of events
needed without overflow.
Signed-off-by: Marcelo Diop-Gonzalez <marcelo827@gmail.com>
Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Right now io_flush_timeouts() checks if the current number of events
is equal to ->timeout.target_seq, but this will miss some timeouts if
there have been more than 1 event added since the last time they were
flushed (possible in io_submit_flush_completions(), for example). Fix
it by recording the last sequence at which timeouts were flushed so
that the number of events seen can be compared to the number of events
needed without overflow.
Signed-off-by: Marcelo Diop-Gonzalez <marcelo827@gmail.com>
Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
| fs/io_uring.c | diffblobblamehistory |