From: Simon Horman <horms@kernel.org>
To: zijianzhang@bytedance.com
Cc: netdev@vger.kernel.org, edumazet@google.com,
willemdebruijn.kernel@gmail.com, cong.wang@bytedance.com,
xiaochun.lu@bytedance.com,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH net-next v7 1/3] sock: support copying cmsgs to the user space in sendmsg
Date: Tue, 9 Jul 2024 10:14:00 +0100 [thread overview]
Message-ID: <20240709091400.GE346094@kernel.org> (raw)
In-Reply-To: <20240708210405.870930-2-zijianzhang@bytedance.com>
+ Dave Miller, Jakub Kicinski, Paolo Abeni, David Ahern, and Jens Axboe
Please generate the CC list Networking for patches using
get_maintainer.pl --git-min-percent=25 this.patch
but omitting LKML.
On Mon, Jul 08, 2024 at 09:04:03PM +0000, zijianzhang@bytedance.com wrote:
> From: Zijian Zhang <zijianzhang@bytedance.com>
>
> Users can pass msg_control as a placeholder to recvmsg, and get some info
> from the kernel upon returning of it, but it's not available for sendmsg.
> Recvmsg uses put_cmsg to copy info back to the user, while ____sys_sendmsg
> creates a kernel copy of msg_control and passes that to the callees,
> put_cmsg in sendmsg path will write into this kernel buffer.
>
> If users want to get info after returning of sendmsg, they typically have
> to call recvmsg on the ERRMSG_QUEUE of the socket, incurring extra system
> call overhead. This commit supports copying cmsg from the kernel space to
> the user space upon returning of sendmsg to mitigate this overhead.
>
> Signed-off-by: Zijian Zhang <zijianzhang@bytedance.com>
> Signed-off-by: Xiaochun Lu <xiaochun.lu@bytedance.com>
...
> diff --git a/net/socket.c b/net/socket.c
> index e416920e9399..6a9c9e24d781 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -2525,8 +2525,43 @@ static int copy_msghdr_from_user(struct msghdr *kmsg,
> return err < 0 ? err : 0;
> }
>
> -static int ____sys_sendmsg(struct socket *sock, struct msghdr *msg_sys,
> - unsigned int flags, struct used_address *used_address,
> +static int sendmsg_copy_cmsg_to_user(struct msghdr *msg_sys,
> + struct user_msghdr __user *umsg)
> +{
> + struct compat_msghdr __user *umsg_compat =
> + (struct compat_msghdr __user *)umsg;
> + unsigned int flags = msg_sys->msg_flags;
> + struct msghdr msg_user = *msg_sys;
> + unsigned long cmsg_ptr;
> + struct cmsghdr *cmsg;
> + int err;
> +
> + msg_user.msg_control_is_user = true;
> + msg_user.msg_control_user = umsg->msg_control;
nit: Sparse seems unhappy about the use of a __user pointer here.
net/socket.c:2540:37: warning: dereference of noderef expression
> + cmsg_ptr = (unsigned long)msg_user.msg_control;
> + for_each_cmsghdr(cmsg, msg_sys) {
> + if (!CMSG_OK(msg_sys, cmsg))
> + break;
> + if (cmsg_copy_to_user(cmsg))
> + put_cmsg(&msg_user, cmsg->cmsg_level, cmsg->cmsg_type,
> + cmsg->cmsg_len - sizeof(*cmsg), CMSG_DATA(cmsg));
> + }
> +
> + err = __put_user((msg_sys->msg_flags & ~MSG_CMSG_COMPAT), COMPAT_FLAGS(umsg));
nit: The line above could be trivially line-wrapped so that it is
no more than 80 columns wide, as is still preferred in Networking code.
Flagged by: checkpatch.pl --max-line-length=80
> + if (err)
> + return err;
> + if (MSG_CMSG_COMPAT & flags)
> + err = __put_user((unsigned long)msg_user.msg_control - cmsg_ptr,
> + &umsg_compat->msg_controllen);
> + else
> + err = __put_user((unsigned long)msg_user.msg_control - cmsg_ptr,
> + &umsg->msg_controllen);
> + return err;
> +}
...
next prev parent reply other threads:[~2024-07-09 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 21:04 [PATCH net-next v7 0/3] net: A lightweight zero-copy notification zijianzhang
2024-07-08 21:04 ` [PATCH net-next v7 1/3] sock: support copying cmsgs to the user space in sendmsg zijianzhang
2024-07-09 9:14 ` Simon Horman [this message]
2024-07-09 17:17 ` Zijian Zhang
2024-07-09 16:40 ` Willem de Bruijn
2024-07-09 17:42 ` Zijian Zhang
2024-07-09 21:30 ` Willem de Bruijn
2024-07-25 1:11 ` Zijian Zhang
2024-07-25 3:08 ` Willem de Bruijn
2024-07-25 4:18 ` Zijian Zhang
2024-07-25 21:34 ` Mina Almasry
2024-07-25 23:50 ` Zijian Zhang
2024-07-26 0:05 ` Zijian Zhang
2024-07-26 17:00 ` Mina Almasry
2024-07-26 20:00 ` Zijian Zhang
2024-07-08 21:04 ` [PATCH net-next v7 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control zijianzhang
2024-07-25 21:59 ` Mina Almasry
2024-07-26 0:01 ` [External] " Zijian Zhang
2024-07-08 21:04 ` [PATCH net-next v7 3/3] selftests: add MSG_ZEROCOPY msg_control notification test zijianzhang
2024-07-09 9:19 ` Simon Horman
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=20240709091400.GE346094@kernel.org \
--to=horms@kernel.org \
--cc=axboe@kernel.dk \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiaochun.lu@bytedance.com \
--cc=zijianzhang@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.