From: Jens Axboe <[email protected]>
To: Gabriel Krisman Bertazi <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH 4/5] io_uring: Introduce IORING_OP_BIND
Date: Fri, 31 May 2024 16:30:54 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/31/24 3:12 PM, Gabriel Krisman Bertazi wrote:
> +int io_bind_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> +{
> + struct io_bind *bind = io_kiocb_to_cmd(req, struct io_bind);
> + struct sockaddr __user *uaddr;
> + struct io_async_msghdr *io;
> + int ret;
> +
> + if (sqe->len || sqe->buf_index || sqe->rw_flags || sqe->splice_fd_in)
> + return -EINVAL;
> +
> + uaddr = u64_to_user_ptr(READ_ONCE(sqe->addr));
> + bind->addr_len = READ_ONCE(sqe->addr2);
> +
> + io = io_msg_alloc_async(req);
> + if (unlikely(!io))
> + return -ENOMEM;
> +
> + ret = move_addr_to_kernel(uaddr, bind->addr_len, &io->addr);
> + if (ret)
> + io_req_msg_cleanup(req, 0);
> + return ret;
> +}
As mentioned in the other patch, I think this can just be:
return move_addr_to_kernel(uaddr, bind->addr_len, &io->addr);
}
and have normal cleanup take care of it.
> +int io_bind(struct io_kiocb *req, unsigned int issue_flags)
> +{
> + struct io_bind *bind = io_kiocb_to_cmd(req, struct io_bind);
> + struct io_async_msghdr *io = req->async_data;
> + int ret;
> +
> + ret = __sys_bind_socket(sock_from_file(req->file), &io->addr, bind->addr_len);
> + if (ret < 0)
> + req_set_fail(req);
> + io_req_set_res(req, ret, 0);
> +
> + return 0;
> +}
Kill the empty line before return.
Outside of those minor nits, patch looks good!
--
Jens Axboe
next prev parent reply other threads:[~2024-05-31 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 21:12 [PATCH 0/5] io_uring: support IORING_OP_BIND and IORING_OP_LISTEN Gabriel Krisman Bertazi
2024-05-31 21:12 ` [PATCH 1/5] io_uring: Fix leak of async data when connect prep fails Gabriel Krisman Bertazi
2024-05-31 21:30 ` Jens Axboe
2024-05-31 23:01 ` Gabriel Krisman Bertazi
2024-05-31 23:07 ` Jens Axboe
2024-05-31 21:12 ` [PATCH 2/5] net: Split a __sys_bind helper for io_uring Gabriel Krisman Bertazi
2024-05-31 22:38 ` Jens Axboe
2024-05-31 21:12 ` [PATCH 3/5] net: Split a __sys_listen " Gabriel Krisman Bertazi
2024-05-31 22:38 ` Jens Axboe
2024-05-31 21:12 ` [PATCH 4/5] io_uring: Introduce IORING_OP_BIND Gabriel Krisman Bertazi
2024-05-31 22:30 ` Jens Axboe [this message]
2024-05-31 21:12 ` [PATCH 5/5] io_uring: Introduce IORING_OP_LISTEN Gabriel Krisman Bertazi
2024-05-31 22:31 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox