public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: netdev@vger.kernel.org, io-uring@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Willem de Bruijn <willemb@google.com>,
	Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v4 3/3] io_uring: Introduce getsockname io_uring cmd
Date: Wed, 26 Nov 2025 09:51:51 -0700	[thread overview]
Message-ID: <4e08b49c-a0e3-4e17-bfdd-a58182b900d9@kernel.dk> (raw)
In-Reply-To: <20251125211806.2673912-4-krisman@suse.de>

On 11/25/25 2:18 PM, Gabriel Krisman Bertazi wrote:
> +static int io_uring_cmd_getsockname(struct socket *sock,
> +				    struct io_uring_cmd *cmd,
> +				    unsigned int issue_flags)
> +{
> +	const struct io_uring_sqe *sqe = cmd->sqe;
> +	struct sockaddr __user *uaddr;
> +	unsigned int peer;
> +	int __user *ulen;
> +
> +	if (sqe->ioprio || sqe->__pad1 || sqe->len || sqe->rw_flags)
> +		return -EINVAL;
> +
> +	uaddr = u64_to_user_ptr(READ_ONCE(sqe->addr));
> +	ulen = u64_to_user_ptr(sqe->addr3);

Missing READ_ONCE() for this one. But I can just amend that, pretty
trivial.

Outside of that, this looks good to me. Bigger question is how to stage
this, in terms of the two networking patches. Jakub?

-- 
Jens Axboe

  reply	other threads:[~2025-11-26 16:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 21:17 [PATCH v4 0/3] Introduce getsockname io_uring_cmd Gabriel Krisman Bertazi
2025-11-25 21:17 ` [PATCH v4 1/3] socket: Unify getsockname and getpeername implementation Gabriel Krisman Bertazi
2025-11-25 21:18 ` [PATCH v4 2/3] socket: Split out a getsockname helper for io_uring Gabriel Krisman Bertazi
2025-11-26  0:24   ` Kuniyuki Iwashima
2025-11-25 21:18 ` [PATCH v4 3/3] io_uring: Introduce getsockname io_uring cmd Gabriel Krisman Bertazi
2025-11-26 16:51   ` Jens Axboe [this message]
2025-11-26 21:47 ` [PATCH v4 0/3] Introduce getsockname io_uring_cmd 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 \
    --in-reply-to=4e08b49c-a0e3-4e17-bfdd-a58182b900d9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.com \
    /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