diff options
author | zhangyi (F) <yi.zhang@huawei.com> | 2019-10-23 10:10:09 +0300 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2019-10-24 07:09:56 +0300 |
commit | a1f58ba46f794b1168d1107befcf3d4b9f9fd453 (patch) | |
tree | 7db113e60fe823f52bf4d743444f9f47898e81d7 /fs/efivarfs | |
parent | ef03681ae8df770745978148a7fb84796ae99cba (diff) | |
download | linux-a1f58ba46f794b1168d1107befcf3d4b9f9fd453.tar.xz |
io_uring: correct timeout req sequence when inserting a new entry
The sequence number of the timeout req (req->sequence) indicate the
expected completion request. Because of each timeout req consume a
sequence number, so the sequence of each timeout req on the timeout
list shouldn't be the same. But now, we may get the same number (also
incorrect) if we insert a new entry before the last one, such as submit
such two timeout reqs on a new ring instance below.
req->sequence
req_1 (count = 2): 2
req_2 (count = 1): 2
Then, if we submit a nop req, req_2 will still timeout even the nop req
finished. This patch fix this problem by adjust the sequence number of
each reordered reqs when inserting a new entry.
Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'fs/efivarfs')
0 files changed, 0 insertions, 0 deletions