io_uring: handle connect -EINPROGRESS like -EAGAIN
Right now we return it to userspace, which means the application has to poll for the socket to be writeable. Let's just treat it like -EAGAIN and have io_uring handle it internally, this makes it much easier to use. Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:
parent
6c6b354914
commit
87f80d623c
|
@ -2242,7 +2242,7 @@ static int io_connect(struct io_kiocb *req, const struct io_uring_sqe *sqe,
|
|||
|
||||
ret = __sys_connect_file(req->file, &io->connect.address, addr_len,
|
||||
file_flags);
|
||||
if (ret == -EAGAIN && force_nonblock) {
|
||||
if ((ret == -EAGAIN || ret == -EINPROGRESS) && force_nonblock) {
|
||||
io = kmalloc(sizeof(*io), GFP_KERNEL);
|
||||
if (!io) {
|
||||
ret = -ENOMEM;
|
||||
|
|
Loading…
Reference in New Issue