All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v9 5/6] vduse: add vq group asid support
Date: Fri, 14 Nov 2025 14:47:52 +0800	[thread overview]
Message-ID: <202511141421.cUqVScv2-lkp@intel.com> (raw)
In-Reply-To: <20251113115558.1277981-6-eperezma@redhat.com>

Hi Eugenio,

kernel test robot noticed the following build warnings:

[auto build test WARNING on linus/master]
[also build test WARNING on v6.18-rc5 next-20251113]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Eugenio-P-rez/vduse-add-v1-API-definition/20251113-200303
base:   linus/master
patch link:    https://lore.kernel.org/r/20251113115558.1277981-6-eperezma%40redhat.com
patch subject: [PATCH v9 5/6] vduse: add vq group asid support
config: i386-randconfig-062-20251114 (https://download.01.org/0day-ci/archive/20251114/202511141421.cUqVScv2-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251114/202511141421.cUqVScv2-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/202511141421.cUqVScv2-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/vdpa/vdpa_user/vduse_dev.c:462:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:462:9: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:462:9: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:919:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:919:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:919:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:938:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:938:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:938:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:959:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:959:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:959:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:980:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:980:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:980:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:1001:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:1001:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:1001:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:1025:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:1025:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:1025:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:1044:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:1044:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:1044:14: sparse:    struct vduse_as *
   drivers/vdpa/vdpa_user/vduse_dev.c:1071:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/vdpa/vdpa_user/vduse_dev.c:1071:14: sparse:    struct vduse_as [noderef] __rcu *
   drivers/vdpa/vdpa_user/vduse_dev.c:1071:14: sparse:    struct vduse_as *
>> drivers/vdpa/vdpa_user/vduse_dev.c:1074:23: sparse: sparse: dereference of noderef expression

vim +462 drivers/vdpa/vdpa_user/vduse_dev.c

   452	
   453	/* Force set the asid to a vq group without a message to the VDUSE device */
   454	static void vduse_set_group_asid_nomsg(struct vduse_dev *dev,
   455					       unsigned int group, unsigned int asid)
   456	{
   457		/*
   458		 * Two concurrent updates to this pointer are valid as they cannot
   459		 * point to an invalid region.  It is ok for them to race as long as
   460		 * the readers see a consistent state through RCU.
   461		 */
 > 462		rcu_assign_pointer(dev->groups[group].as, &dev->as[asid]);
   463	}
   464	

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

  parent reply	other threads:[~2025-11-14  6:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 11:55 [PATCH v9 0/6] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-11-13 11:55 ` [PATCH v9 1/6] vduse: add v1 API definition Eugenio Pérez
2025-11-13 11:55 ` [PATCH v9 2/6] vduse: add vq group support Eugenio Pérez
2025-11-13 11:55 ` [PATCH v9 3/6] vduse: return internal vq group struct as map token Eugenio Pérez
2025-11-13 11:55 ` [PATCH v9 4/6] vduse: refactor vdpa_dev_add for goto err handling Eugenio Pérez
2025-11-13 11:55 ` [PATCH v9 5/6] vduse: add vq group asid support Eugenio Pérez
2025-11-14  0:55   ` Jason Wang
2025-11-14 11:25     ` Eugenio Perez Martin
2025-11-17  4:23       ` Jason Wang
2025-11-17 12:15         ` Eugenio Perez Martin
2025-11-19  2:38           ` Jason Wang
2025-11-19  9:26             ` Eugenio Perez Martin
2025-11-19  9:32               ` Michael S. Tsirkin
2025-11-19 10:38                 ` Eugenio Perez Martin
2025-11-19 12:29                   ` Michael S. Tsirkin
2025-11-20  1:37               ` Jason Wang
2025-12-03  7:57                 ` Eugenio Perez Martin
2025-12-04  2:15                   ` Jason Wang
2025-12-04  8:32                     ` Eugenio Perez Martin
2025-12-05  1:51                       ` Jason Wang
2025-12-05 15:30                         ` Eugenio Perez Martin
2025-12-08  2:58                           ` Jason Wang
2025-11-17 10:50       ` Michael S. Tsirkin
2025-11-17 12:16         ` Eugenio Perez Martin
2025-11-14  6:46   ` kernel test robot
2025-11-14  6:47   ` kernel test robot [this message]
2025-11-17  3:10   ` 谢永吉
2025-11-17  9:08     ` Eugenio Perez Martin
2025-11-13 11:55 ` [PATCH v9 6/6] vduse: bump version number Eugenio Pérez

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=202511141421.cUqVScv2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=eperezma@redhat.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.