From: kernel test robot <lkp@intel.com>
To: Daniel Jurgens <danielj@nvidia.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, mst@redhat.com,
jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
virtualization@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jiri@nvidia.com, Daniel Jurgens <danielj@nvidia.com>
Subject: Re: [PATCH net-next v2 2/6] virtio_net: Remove command data from control_buf
Date: Fri, 29 Mar 2024 05:58:14 +0800 [thread overview]
Message-ID: <202403290542.gM5D7hMG-lkp@intel.com> (raw)
In-Reply-To: <20240328044715.266641-3-danielj@nvidia.com>
Hi Daniel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Daniel-Jurgens/virtio_net-Store-RSS-setting-in-virtnet_info/20240328-125022
base: net-next/main
patch link: https://lore.kernel.org/r/20240328044715.266641-3-danielj%40nvidia.com
patch subject: [PATCH net-next v2 2/6] virtio_net: Remove command data from control_buf
config: x86_64-randconfig-122-20240328 (https://download.01.org/0day-ci/archive/20240329/202403290542.gM5D7hMG-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240329/202403290542.gM5D7hMG-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202403290542.gM5D7hMG-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/virtio_net.c:3978:20: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __virtio64 @@
drivers/net/virtio_net.c:3978:20: sparse: expected unsigned long long [usertype]
drivers/net/virtio_net.c:3978:20: sparse: got restricted __virtio64
vim +3978 drivers/net/virtio_net.c
3968
3969 static int virtnet_set_guest_offloads(struct virtnet_info *vi, u64 offloads)
3970 {
3971 u64 *_offloads __free(kfree) = NULL;
3972 struct scatterlist sg;
3973
3974 _offloads = kzalloc(sizeof(*_offloads), GFP_KERNEL);
3975 if (!_offloads)
3976 return -ENOMEM;
3977
> 3978 *_offloads = cpu_to_virtio64(vi->vdev, offloads);
3979
3980 sg_init_one(&sg, _offloads, sizeof(*_offloads));
3981
3982 if (!virtnet_send_command(vi, VIRTIO_NET_CTRL_GUEST_OFFLOADS,
3983 VIRTIO_NET_CTRL_GUEST_OFFLOADS_SET, &sg)) {
3984 dev_warn(&vi->dev->dev, "Fail to set guest offload.\n");
3985 return -EINVAL;
3986 }
3987
3988 return 0;
3989 }
3990
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-03-28 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 4:47 [PATCH net-next v2 0/6] Remove RTNL lock protection of CVQ Daniel Jurgens
2024-03-28 4:47 ` [PATCH net-next v2 1/6] virtio_net: Store RSS setting in virtnet_info Daniel Jurgens
2024-03-28 4:47 ` [PATCH net-next v2 2/6] virtio_net: Remove command data from control_buf Daniel Jurgens
2024-03-28 21:58 ` kernel test robot [this message]
2024-03-28 4:47 ` [PATCH net-next v2 3/6] virtio_net: Add a lock for the command VQ Daniel Jurgens
2024-03-28 4:47 ` [PATCH net-next v2 4/6] virtio_net: Do DIM update for specified queue only Daniel Jurgens
2024-03-28 4:57 ` Heng Qi
2024-03-28 5:12 ` Dan Jurgens
2024-03-28 4:47 ` [PATCH net-next v2 5/6] virtio_net: Add a lock for per queue RX coalesce Daniel Jurgens
2024-03-28 4:47 ` [PATCH net-next v2 6/6] virtio_net: Remove rtnl lock protection of command buffers Daniel Jurgens
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=202403290542.gM5D7hMG-lkp@intel.com \
--to=lkp@intel.com \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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.