netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Jurgens <danielj@nvidia.com>,
	netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
	alex.williamson@redhat.com, pabeni@redhat.com
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	virtualization@lists.linux.dev, parav@nvidia.com,
	shshitrit@nvidia.com, yohadt@nvidia.com,
	xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	shameerali.kolothum.thodi@huawei.com, jgg@ziepe.ca,
	kevin.tian@intel.com, kuba@kernel.org, andrew+netdev@lunn.ch,
	edumazet@google.com, Daniel Jurgens <danielj@nvidia.com>
Subject: Re: [PATCH net-next v4 01/12] virtio_pci: Remove supported_cap size build assert
Date: Tue, 14 Oct 2025 15:04:09 +0800	[thread overview]
Message-ID: <202510141404.P5SMiruH-lkp@intel.com> (raw)
In-Reply-To: <20251013152742.619423-2-danielj@nvidia.com>

Hi Daniel,

kernel test robot noticed the following build errors:

[auto build test ERROR on net-next/main]

url:    https://github.com/intel-lab-lkp/linux/commits/Daniel-Jurgens/virtio_pci-Remove-supported_cap-size-build-assert/20251014-004146
base:   net-next/main
patch link:    https://lore.kernel.org/r/20251013152742.619423-2-danielj%40nvidia.com
patch subject: [PATCH net-next v4 01/12] virtio_pci: Remove supported_cap size build assert
config: s390-randconfig-001-20251014 (https://download.01.org/0day-ci/archive/20251014/202510141404.P5SMiruH-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 39f292ffa13d7ca0d1edff27ac8fd55024bb4d19)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251014/202510141404.P5SMiruH-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/202510141404.P5SMiruH-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/virtio/virtio_pci_modern.c:326:26: error: no member named 'support_caps' in 'struct virtio_admin_cmd_query_cap_id_result'
     326 |         if (!(le64_to_cpu(data->support_caps[0]) & (1 << VIRTIO_DEV_PARTS_CAP)))
         |                           ~~~~  ^
   include/linux/byteorder/generic.h:87:21: note: expanded from macro 'le64_to_cpu'
      87 | #define le64_to_cpu __le64_to_cpu
         |                     ^
   1 error generated.


vim +326 drivers/virtio/virtio_pci_modern.c

   304	
   305	static void virtio_pci_admin_cmd_cap_init(struct virtio_device *virtio_dev)
   306	{
   307		struct virtio_pci_device *vp_dev = to_vp_device(virtio_dev);
   308		struct virtio_admin_cmd_query_cap_id_result *data;
   309		struct virtio_admin_cmd cmd = {};
   310		struct scatterlist result_sg;
   311		int ret;
   312	
   313		data = kzalloc(sizeof(*data), GFP_KERNEL);
   314		if (!data)
   315			return;
   316	
   317		sg_init_one(&result_sg, data, sizeof(*data));
   318		cmd.opcode = cpu_to_le16(VIRTIO_ADMIN_CMD_CAP_ID_LIST_QUERY);
   319		cmd.group_type = cpu_to_le16(VIRTIO_ADMIN_GROUP_TYPE_SELF);
   320		cmd.result_sg = &result_sg;
   321	
   322		ret = vp_modern_admin_cmd_exec(virtio_dev, &cmd);
   323		if (ret)
   324			goto end;
   325	
 > 326		if (!(le64_to_cpu(data->support_caps[0]) & (1 << VIRTIO_DEV_PARTS_CAP)))
   327			goto end;
   328	
   329		virtio_pci_admin_cmd_dev_parts_objects_enable(virtio_dev);
   330	end:
   331		kfree(data);
   332	}
   333	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-10-14  7:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 15:27 [PATCH net-next v4 00/12] virtio_net: Add ethtool flow rules support Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 01/12] virtio_pci: Remove supported_cap size build assert Daniel Jurgens
2025-10-13 16:38   ` [External] : " ALOK TIWARI
2025-10-13 17:57     ` Dan Jurgens
2025-10-14  5:28   ` kernel test robot
2025-10-14  7:04   ` kernel test robot [this message]
2025-10-13 15:27 ` [PATCH net-next v4 02/12] virtio: Add config_op for admin commands Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 03/12] virtio: Expose generic device capability operations Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 04/12] virtio: Expose object create and destroy API Daniel Jurgens
2025-10-13 16:25   ` [External] : " ALOK TIWARI
2025-10-13 15:27 ` [PATCH net-next v4 05/12] virtio_net: Query and set flow filter caps Daniel Jurgens
2025-10-14  6:32   ` kernel test robot
2025-10-13 15:27 ` [PATCH net-next v4 06/12] virtio_net: Create a FF group for ethtool steering Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 07/12] virtio_net: Implement layer 2 ethtool flow rules Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 08/12] virtio_net: Use existing classifier if possible Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 09/12] virtio_net: Implement IPv4 ethtool flow rules Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 10/12] virtio_net: Add support for IPv6 ethtool steering Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 11/12] virtio_net: Add support for TCP and UDP ethtool rules Daniel Jurgens
2025-10-13 15:27 ` [PATCH net-next v4 12/12] virtio_net: Add get ethtool flow rules ops 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=202510141404.P5SMiruH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=danielj@nvidia.com \
    --cc=edumazet@google.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kuba@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=parav@nvidia.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=shshitrit@nvidia.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yohadt@nvidia.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).