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/dma-buf/sw_sync.c:88:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Sat, 02 May 2026 14:29:56 +0800	[thread overview]
Message-ID: <202605021435.i9s35ZfI-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   cd546f7ae2fce8b695c834143b50e712d62ebed8
commit: f4cc3ab824d6772a48ca9d9c74ac623b3309985d dma-buf: protected fence ops by RCU v8
date:   10 weeks ago
config: sparc64-randconfig-r113-20260430 (https://download.01.org/0day-ci/archive/20260502/202605021435.i9s35ZfI-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260502/202605021435.i9s35ZfI-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/202605021435.i9s35ZfI-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/dma-buf/sw_sync.c: note: in included file (through include/linux/security.h, include/linux/perf_event.h, include/linux/trace_events.h, include/trace/trace_events.h, ...):
   include/linux/bpf.h:2302:16: sparse: sparse: Expected ) in function call
   include/linux/bpf.h:2302:16: sparse: sparse: got __VA_OPT__
   include/linux/bpf.h:2302:16: sparse: sparse: Expected ) in function call
   include/linux/bpf.h:2302:16: sparse: sparse: got __VA_OPT__
   include/linux/bpf.h:2302:16: sparse: sparse: Expected ) in function call
   include/linux/bpf.h:2302:16: sparse: sparse: got __VA_OPT__
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: Expected ) in function call
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: got ,
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: undefined identifier '_res'
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: undefined identifier '_res'
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/dma-buf/sw_sync.c:104:15: sparse: sparse: undefined identifier '_res'
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: undefined identifier '_res'
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: undefined identifier '_res'
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: undefined identifier '__VA_OPT__'
   drivers/dma-buf/sw_sync.c:255:14: sparse: sparse: undefined identifier '_res'
>> drivers/dma-buf/sw_sync.c:88:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const [noderef] __rcu *
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const *
>> drivers/dma-buf/sw_sync.c:88:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const [noderef] __rcu *
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const *
>> drivers/dma-buf/sw_sync.c:88:24: sparse: sparse: incompatible types in comparison expression (different address spaces):
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const [noderef] __rcu *
   drivers/dma-buf/sw_sync.c:88:24: sparse:    struct dma_fence_ops const *

vim +88 drivers/dma-buf/sw_sync.c

aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  85  
f54d1867005c33 drivers/dma-buf/sw_sync.c         Chris Wilson    2016-10-25  86  static inline struct sync_pt *dma_fence_to_sync_pt(struct dma_fence *fence)
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  87  {
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31 @88  	if (fence->ops != &timeline_fence_ops)
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  89  		return NULL;
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  90  	return container_of(fence, struct sync_pt, base);
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  91  }
aff9da10e218c5 drivers/staging/android/sw_sync.c Gustavo Padovan 2016-05-31  92  

:::::: The code at line 88 was first introduced by commit
:::::: aff9da10e218c54f5ffc8bcb66c9837135074190 staging/android: make sync_timeline internal to sw_sync

:::::: TO: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

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

                 reply	other threads:[~2026-05-02  6:30 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=202605021435.i9s35ZfI-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