public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Christian König " <christian.koenig@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
	Boris Brezillon <bbrezillon@kernel.org>
Subject: drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:95:20: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Fri, 01 May 2026 07:28:27 +0800	[thread overview]
Message-ID: <202605010713.u3viFnvV-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   08d0d3466664000ba0670e0ef0d447f23459e0d4
commit: f4cc3ab824d6772a48ca9d9c74ac623b3309985d dma-buf: protected fence ops by RCU v8
date:   9 weeks ago
config: x86_64-randconfig-122-20260430 (https://download.01.org/0day-ci/archive/20260501/202605010713.u3viFnvV-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260501/202605010713.u3viFnvV-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
| Fixes: f4cc3ab824d6 ("dma-buf: protected fence ops by RCU v8")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605010713.u3viFnvV-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c: note: in included file (through include/linux/i2c.h, drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu_ras_eeprom.h, drivers/gpu/drm/amd/amdgpu/../amdgpu/amdgpu_ras.h, ...):
   include/linux/acpi.h:69:18: sparse: sparse: Expected ) in function call
   include/linux/acpi.h:69:18: sparse: sparse: got ,
   include/linux/acpi.h:69:18: sparse: sparse: Expected ) in function call
   include/linux/acpi.h:69:18: sparse: sparse: got ,
   include/linux/acpi.h:69:18: sparse: sparse: Expected ) in function call
   include/linux/acpi.h:69:18: sparse: sparse: got ,
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: Expected ) in function call
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: got ,
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: Expected ) in function call
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: got ,
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: Expected ) in function call
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: got ,
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: undefined identifier '_res'
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: undefined identifier '_res'
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:70:17: sparse: sparse: undefined identifier '_res'
>> drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:95:20: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:95:20: sparse:    struct dma_fence_ops const [noderef] __rcu *
   drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c:95:20: sparse:    struct dma_fence_ops const *

vim +95 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c

d8d019ccffb838 Felix Kuehling       2018-02-06   86  
d8d019ccffb838 Felix Kuehling       2018-02-06   87  struct amdgpu_amdkfd_fence *to_amdgpu_amdkfd_fence(struct dma_fence *f)
d8d019ccffb838 Felix Kuehling       2018-02-06   88  {
d8d019ccffb838 Felix Kuehling       2018-02-06   89  	struct amdgpu_amdkfd_fence *fence;
d8d019ccffb838 Felix Kuehling       2018-02-06   90  
d8d019ccffb838 Felix Kuehling       2018-02-06   91  	if (!f)
d8d019ccffb838 Felix Kuehling       2018-02-06   92  		return NULL;
d8d019ccffb838 Felix Kuehling       2018-02-06   93  
d8d019ccffb838 Felix Kuehling       2018-02-06   94  	fence = container_of(f, struct amdgpu_amdkfd_fence, base);
bf2ad4fb8adca8 Srinivasan Shanmugam 2023-12-27  @95  	if (f->ops == &amdkfd_fence_ops)
d8d019ccffb838 Felix Kuehling       2018-02-06   96  		return fence;
d8d019ccffb838 Felix Kuehling       2018-02-06   97  
d8d019ccffb838 Felix Kuehling       2018-02-06   98  	return NULL;
d8d019ccffb838 Felix Kuehling       2018-02-06   99  }
d8d019ccffb838 Felix Kuehling       2018-02-06  100  

:::::: The code at line 95 was first introduced by commit
:::::: bf2ad4fb8adca89374b54b225d494e0b1956dbea drm/amdgpu: Drop 'fence' check in 'to_amdgpu_amdkfd_fence()'

:::::: TO: Srinivasan Shanmugam <srinivasan.shanmugam@amd.com>
:::::: CC: Alex Deucher <alexander.deucher@amd.com>

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

                 reply	other threads:[~2026-04-30 23:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202605010713.u3viFnvV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bbrezillon@kernel.org \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tvrtko.ursulin@igalia.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