From: kernel test robot <lkp@intel.com>
To: Bobby Eshleman <bobby.eshleman@bytedance.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC net-next v2 3/4] vsock: Add lockless sendmsg() support
Date: Fri, 14 Apr 2023 10:09:44 +0800 [thread overview]
Message-ID: <202304140923.cXElTOcl-lkp@intel.com> (raw)
In-Reply-To: <20230413-b4-vsock-dgram-v2-3-079cc7cee62e@bytedance.com>
Hi Bobby,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on ed72bd5a6790a0c3747cb32b0427f921bd03bb71]
url: https://github.com/intel-lab-lkp/linux/commits/Bobby-Eshleman/virtio-vsock-support-dgram/20230414-082831
base: ed72bd5a6790a0c3747cb32b0427f921bd03bb71
patch link: https://lore.kernel.org/r/20230413-b4-vsock-dgram-v2-3-079cc7cee62e%40bytedance.com
patch subject: [PATCH RFC net-next v2 3/4] vsock: Add lockless sendmsg() support
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230414/202304140923.cXElTOcl-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/de4d5e13dd5c747996abbc4e9ce38eeb3093ea01
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Bobby-Eshleman/virtio-vsock-support-dgram/20230414-082831
git checkout de4d5e13dd5c747996abbc4e9ce38eeb3093ea01
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=m68k SHELL=/bin/bash net/vmw_vsock/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304140923.cXElTOcl-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/vmw_vsock/af_vsock.c:247:5: warning: no previous prototype for 'vsock_remote_addr_update' [-Wmissing-prototypes]
247 | int vsock_remote_addr_update(struct vsock_sock *vsk, struct sockaddr_vm *src)
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/vsock_remote_addr_update +247 net/vmw_vsock/af_vsock.c
245
246 /* The socket lock must be held by the caller */
> 247 int vsock_remote_addr_update(struct vsock_sock *vsk, struct sockaddr_vm *src)
248 {
249 struct sockaddr_vm_rcu *old, *new;
250
251 new = kmalloc(sizeof(*new), GFP_KERNEL);
252 if (!new)
253 return -ENOMEM;
254
255 memcpy(&new->addr, src, sizeof(new->addr));
256 old = rcu_replace_pointer(vsk->remote_addr, new, lockdep_sock_is_held(sk_vsock(vsk)));
257 kfree_rcu(old, rcu);
258
259 return 0;
260 }
261
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-14 2:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 0:25 [PATCH RFC net-next v2 0/4] virtio/vsock: support datagrams Bobby Eshleman
2023-04-14 0:25 ` [PATCH RFC net-next v2 1/4] virtio/vsock: support dgram Bobby Eshleman
2023-04-19 9:29 ` Stefano Garzarella
2023-04-19 9:29 ` Stefano Garzarella
2023-04-14 0:25 ` [PATCH RFC net-next v2 2/4] virtio/vsock: add VIRTIO_VSOCK_F_DGRAM feature bit Bobby Eshleman
2023-04-14 8:47 ` Alvaro Karsz
2023-04-14 8:47 ` Alvaro Karsz
2023-04-14 10:28 ` Bobby Eshleman
2023-04-19 9:30 ` Stefano Garzarella
2023-04-19 9:30 ` Stefano Garzarella
2023-04-15 9:51 ` Bobby Eshleman
2023-04-14 0:25 ` [PATCH RFC net-next v2 3/4] vsock: Add lockless sendmsg() support Bobby Eshleman
2023-04-14 2:09 ` kernel test robot [this message]
2023-04-14 3:32 ` kernel test robot
2023-04-15 6:13 ` kernel test robot
2023-04-19 9:30 ` Stefano Garzarella
2023-04-19 9:30 ` Stefano Garzarella
2023-04-15 10:30 ` Bobby Eshleman
2023-04-28 10:29 ` Stefano Garzarella
2023-04-28 10:29 ` Stefano Garzarella
2023-04-15 17:29 ` Bobby Eshleman
2023-05-03 12:09 ` Stefano Garzarella
2023-05-03 12:09 ` Stefano Garzarella
2023-04-14 0:26 ` [PATCH RFC net-next v2 4/4] tests: add vsock dgram tests Bobby Eshleman
2023-04-14 11:18 ` [PATCH RFC net-next v2 0/4] virtio/vsock: support datagrams Bobby Eshleman
2023-04-19 10:00 ` Stefano Garzarella
2023-04-19 10:00 ` Stefano Garzarella
2023-04-15 7:13 ` Bobby Eshleman
2023-04-15 7:13 ` [virtio-dev] " Bobby Eshleman
2023-04-28 10:43 ` Stefano Garzarella
2023-04-28 10:43 ` Stefano Garzarella
2023-04-28 10:43 ` [virtio-dev] " Stefano Garzarella
2023-04-15 15:55 ` Bobby Eshleman
2023-04-15 15:55 ` [virtio-dev] " Bobby Eshleman
2023-05-03 12:13 ` Stefano Garzarella
2023-05-03 12:13 ` [virtio-dev] " Stefano Garzarella
2023-05-03 12:13 ` Stefano Garzarella
2023-04-14 5:16 [PATCH RFC net-next v2 3/4] vsock: Add lockless sendmsg() support kernel test robot
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=202304140923.cXElTOcl-lkp@intel.com \
--to=lkp@intel.com \
--cc=bobby.eshleman@bytedance.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.