diff options
author | 2021-08-14 09:04:40 -0600 | |
---|---|---|
committer | 2021-08-14 12:38:21 -0600 | |
commit | 21f965221e7c42609521342403e8fb91b8b3e76e (patch) | |
tree | f680b17ee19d8069fafac58f8bcfca3aa4782e75 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | tools/io_uring/io_uring-cp: sync with liburing example (diff) | |
download | wireguard-linux-21f965221e7c42609521342403e8fb91b8b3e76e.tar.xz wireguard-linux-21f965221e7c42609521342403e8fb91b8b3e76e.zip |
io_uring: only assign io_uring_enter() SQPOLL error in actual error case
If an SQPOLL based ring is newly created and an application issues an
io_uring_enter(2) system call on it, then we can return a spurious
-EOWNERDEAD error. This happens because there's nothing to submit, and
if the caller doesn't specify any other action, the initial error
assignment of -EOWNERDEAD never gets overwritten. This causes us to
return it directly, even if it isn't valid.
Move the error assignment into the actual failure case instead.
Cc: stable@vger.kernel.org
Fixes: d9d05217cb69 ("io_uring: stop SQPOLL submit on creator's death")
Reported-by: Sherlock Holo sherlockya@gmail.com
Link: https://github.com/axboe/liburing/issues/413
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions