From: Jakub Kicinski <kuba@kernel.org>
To: zijianzhang@bytedance.com
Cc: netdev@vger.kernel.org, edumazet@google.com,
willemdebruijn.kernel@gmail.com, davem@davemloft.net,
cong.wang@bytedance.com, xiaochun.lu@bytedance.com
Subject: Re: [PATCH net-next v2 0/3] net: A lightweight zero-copy notification
Date: Fri, 19 Apr 2024 20:47:54 -0700 [thread overview]
Message-ID: <20240419204754.3f3b7347@kernel.org> (raw)
In-Reply-To: <20240419214819.671536-1-zijianzhang@bytedance.com>
On Fri, 19 Apr 2024 21:48:16 +0000 zijianzhang@bytedance.com wrote:
> Original title is "net: socket sendmsg MSG_ZEROCOPY_UARG"
> https://lore.kernel.org/all/
> 20240409205300.1346681-2-zijianzhang@bytedance.com/
AFAICT sparse reports this new warning:
net/core/sock.c:2864:26: warning: incorrect type in assignment (different address spaces)
net/core/sock.c:2864:26: expected void [noderef] __user *usr_addr
net/core/sock.c:2864:26: got void *
--
pw-bot: cr
next prev parent reply other threads:[~2024-04-20 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 21:48 [PATCH net-next v2 0/3] net: A lightweight zero-copy notification zijianzhang
2024-04-19 21:48 ` [PATCH net-next v2 1/3] selftests: fix OOM problem in msg_zerocopy selftest zijianzhang
2024-04-21 15:16 ` Willem de Bruijn
2024-04-23 19:31 ` [External] " Zijian Zhang
2024-04-19 21:48 ` [PATCH net-next v2 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control zijianzhang
2024-04-21 15:45 ` Willem de Bruijn
2024-04-23 19:51 ` [External] " Zijian Zhang
2024-04-23 3:16 ` kernel test robot
2024-04-19 21:48 ` [PATCH net-next v2 3/3] selftests: add MSG_ZEROCOPY msg_control notification test zijianzhang
2024-04-20 3:47 ` Jakub Kicinski [this message]
2024-04-23 19:29 ` [External] Re: [PATCH net-next v2 0/3] net: A lightweight zero-copy notification Zijian Zhang
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=20240419204754.3f3b7347@kernel.org \
--to=kuba@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).