* [PATCH] io_uring: handle connect -EINPROGRESS like -EAGAIN
@ 2019-12-03 18:25 Jens Axboe
0 siblings, 0 replies; only message in thread
From: Jens Axboe @ 2019-12-03 18:25 UTC (permalink / raw)
To: io-uring
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 <[email protected]>
---
diff --git a/fs/io_uring.c b/fs/io_uring.c
index f7985f270d4a..6c22a277904e 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -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;
--
Jens Axboe
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-03 18:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-03 18:25 [PATCH] io_uring: handle connect -EINPROGRESS like -EAGAIN Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox