All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v4 12/17] virtio/vsock: rest of SOCK_SEQPACKET support
Date: Tue, 09 Feb 2021 12:34:38 +0800	[thread overview]
Message-ID: <202102091228.imhertUv-lkp@intel.com> (raw)
In-Reply-To: <20210207151747.805754-1-arseny.krasnov@kaspersky.com>

[-- Attachment #1: Type: text/plain, Size: 3691 bytes --]

Hi Arseny,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on linus/master]
[cannot apply to vhost/linux-next v5.11-rc6 next-20210125]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Arseny-Krasnov/virtio-vsock-introduce-SOCK_SEQPACKET-support/20210207-232655
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 61556703b610a104de324e4f061dc6cf7b218b46
config: i386-randconfig-s001-20210209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-215-g0fb77bb6-dirty
        # https://github.com/0day-ci/linux/commit/0bfa48046cf3aa71cde18727f1ac90448308bfdd
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Arseny-Krasnov/virtio-vsock-introduce-SOCK_SEQPACKET-support/20210207-232655
        git checkout 0bfa48046cf3aa71cde18727f1ac90448308bfdd
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


"sparse warnings: (new ones prefixed by >>)"
   net/vmw_vsock/virtio_transport_common.c:430:31: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le32 [usertype] msg_cnt @@     got unsigned int [usertype] next_tx_msg_cnt @@
   net/vmw_vsock/virtio_transport_common.c:430:31: sparse:     expected restricted __le32 [usertype] msg_cnt
   net/vmw_vsock/virtio_transport_common.c:430:31: sparse:     got unsigned int [usertype] next_tx_msg_cnt
>> net/vmw_vsock/virtio_transport_common.c:431:28: sparse: sparse: incorrect type in initializer (different base types) @@     expected restricted __le32 [usertype] msg_len @@     got unsigned int [usertype] len @@
   net/vmw_vsock/virtio_transport_common.c:431:28: sparse:     expected restricted __le32 [usertype] msg_len
   net/vmw_vsock/virtio_transport_common.c:431:28: sparse:     got unsigned int [usertype] len

vim +431 net/vmw_vsock/virtio_transport_common.c

   416	
   417	static int virtio_transport_seqpacket_send_ctrl(struct vsock_sock *vsk,
   418							int type,
   419							size_t len,
   420							int flags)
   421	{
   422		struct virtio_vsock_sock *vvs = vsk->trans;
   423		struct virtio_vsock_pkt_info info = {
   424			.op = type,
   425			.vsk = vsk,
   426			.pkt_len = sizeof(struct virtio_vsock_seq_hdr)
   427		};
   428	
   429		struct virtio_vsock_seq_hdr seq_hdr = {
   430			.msg_cnt = vvs->next_tx_msg_cnt,
 > 431			.msg_len = len
   432		};
   433	
   434		struct kvec seq_hdr_kiov = {
   435			.iov_base = (void *)&seq_hdr,
   436			.iov_len = sizeof(struct virtio_vsock_seq_hdr)
   437		};
   438	
   439		struct msghdr msg = {0};
   440	
   441		//XXX: do we need 'vsock_transport_send_notify_data' pointer?
   442		if (vsock_wait_space(sk_vsock(vsk),
   443				     sizeof(struct virtio_vsock_seq_hdr),
   444				     flags, NULL))
   445			return -1;
   446	
   447		iov_iter_kvec(&msg.msg_iter, WRITE, &seq_hdr_kiov, 1, sizeof(seq_hdr));
   448	
   449		info.msg = &msg;
   450		vvs->next_tx_msg_cnt++;
   451	
   452		return virtio_transport_send_pkt_info(vsk, &info);
   453	}
   454	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35484 bytes --]

  reply	other threads:[~2021-02-09  4:34 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-07 15:12 [RFC PATCH v4 00/17] virtio/vsock: introduce SOCK_SEQPACKET support Arseny Krasnov
2021-02-07 15:14 ` [RFC PATCH v4 01/17] af_vsock: update functions for connectible socket Arseny Krasnov
2021-02-11 10:52   ` Stefano Garzarella
2021-02-11 10:52     ` Stefano Garzarella
2021-02-07 15:14 ` [RFC PATCH v4 02/17] af_vsock: separate wait data loop Arseny Krasnov
2021-02-11 11:24   ` Stefano Garzarella
2021-02-11 11:24     ` Stefano Garzarella
2021-02-11 15:11   ` Jorgen Hansen
2021-02-11 15:11     ` Jorgen Hansen
2021-02-16  6:58     ` Arseny Krasnov
2021-02-07 15:15 ` [RFC PATCH v4 03/17] af_vsock: separate receive " Arseny Krasnov
2021-02-11 11:37   ` Stefano Garzarella
2021-02-11 11:37     ` Stefano Garzarella
2021-02-07 15:15 ` [RFC PATCH v4 04/17] af_vsock: implement SEQPACKET receive loop Arseny Krasnov
2021-02-11 11:47   ` Stefano Garzarella
2021-02-11 11:47     ` Stefano Garzarella
2021-02-07 15:15 ` [RFC PATCH v4 05/17] af_vsock: separate wait space loop Arseny Krasnov
2021-02-07 16:58   ` kernel test robot
2021-02-11 12:14   ` Stefano Garzarella
2021-02-11 12:14     ` Stefano Garzarella
2021-02-07 15:15 ` [RFC PATCH v4 06/17] af_vsock: implement send logic for SEQPACKET Arseny Krasnov
2021-02-11 12:17   ` Stefano Garzarella
2021-02-11 12:17     ` Stefano Garzarella
2021-02-07 15:16 ` [RFC PATCH v4 07/17] af_vsock: rest of SEQPACKET support Arseny Krasnov
2021-02-11 12:27   ` Stefano Garzarella
2021-02-11 12:27     ` Stefano Garzarella
2021-02-15  9:11     ` Arseny Krasnov
2021-02-07 15:16 ` [RFC PATCH v4 08/17] af_vsock: update comments for stream sockets Arseny Krasnov
2021-02-11 13:19   ` Stefano Garzarella
2021-02-11 13:19     ` Stefano Garzarella
2021-02-07 15:16 ` [RFC PATCH v4 09/17] virtio/vsock: dequeue callback for SOCK_SEQPACKET Arseny Krasnov
2021-02-11 13:54   ` Stefano Garzarella
2021-02-11 13:54     ` Stefano Garzarella
2021-02-11 14:03     ` Stefano Garzarella
2021-02-11 14:03       ` Stefano Garzarella
2021-02-07 15:17 ` [RFC PATCH v4 10/17] virtio/vsock: fetch length for SEQPACKET record Arseny Krasnov
2021-02-11 13:58   ` Stefano Garzarella
2021-02-11 13:58     ` Stefano Garzarella
2021-02-07 15:17 ` [RFC PATCH v4 11/17] virtio/vsock: add SEQPACKET receive logic Arseny Krasnov
2021-02-07 15:17 ` [RFC PATCH v4 12/17] virtio/vsock: rest of SOCK_SEQPACKET support Arseny Krasnov
2021-02-09  4:34   ` kernel test robot [this message]
2021-02-11 11:00   ` Arseny Krasnov
2021-02-11 14:29   ` Stefano Garzarella
2021-02-11 14:29     ` Stefano Garzarella
2021-02-07 15:18 ` [RFC PATCH v4 13/17] virtio/vsock: setup SEQPACKET ops for transport Arseny Krasnov
2021-02-07 15:18 ` [RFC PATCH v4 14/17] vhost/vsock: " Arseny Krasnov
2021-02-07 15:18 ` [RFC PATCH v4 15/17] vsock_test: add SOCK_SEQPACKET tests Arseny Krasnov
2021-02-07 15:18 ` [RFC PATCH v4 16/17] loopback/vsock: setup SEQPACKET ops for transport Arseny Krasnov
2021-02-11 14:31   ` Stefano Garzarella
2021-02-11 14:31     ` Stefano Garzarella
2021-02-07 15:19 ` [RFC PATCH v4 17/17] virtio/vsock: simplify credit update function API Arseny Krasnov
2021-02-11 14:39   ` Stefano Garzarella
2021-02-11 14:39     ` Stefano Garzarella
2021-02-07 16:20 ` [RFC PATCH v4 00/17] virtio/vsock: introduce SOCK_SEQPACKET support Michael S. Tsirkin
2021-02-07 16:20   ` Michael S. Tsirkin
2021-02-08  6:32   ` Arseny Krasnov
2021-02-11 14:57     ` Stefano Garzarella
2021-02-11 14:57       ` Stefano Garzarella
2021-02-12  6:11       ` Arseny Krasnov
2021-02-12  8:07         ` Stefano Garzarella
2021-02-12  8:07           ` Stefano Garzarella

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=202102091228.imhertUv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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.