From: kernel test robot <lkp@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
phasta@mailbox.org, matthew.brost@intel.com,
sumit.semwal@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH 1/8] dma-buf: protected fence ops by RCU v7
Date: Sat, 21 Feb 2026 22:15:24 +0800 [thread overview]
Message-ID: <202602212248.xPSr8tt8-lkp@intel.com> (raw)
In-Reply-To: <20260219160822.1529-2-christian.koenig@amd.com>
Hi Christian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[cannot apply to drm-i915/for-linux-next drm-i915/for-linux-next-fixes drm-xe/drm-xe-next linus/master v6.19 next-20260220]
[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/Christian-K-nig/dma-buf-detach-fence-ops-on-signal-v2/20260220-010804
base: https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
patch link: https://lore.kernel.org/r/20260219160822.1529-2-christian.koenig%40amd.com
patch subject: [PATCH 1/8] dma-buf: protected fence ops by RCU v7
config: hexagon-randconfig-r121-20260221 (https://download.01.org/0day-ci/archive/20260221/202602212248.xPSr8tt8-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project e86750b29fa0ff207cd43213d66dabe565417638)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260221/202602212248.xPSr8tt8-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/202602212248.xPSr8tt8-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/dma-buf/dma-fence-array.c: note: in included file (through include/linux/dma-fence-array.h):
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
include/linux/dma-fence.h:732:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:732:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:732:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
--
drivers/dma-buf/dma-resv.c: note: in included file (through include/linux/dma-resv.h):
>> include/linux/dma-fence.h:721:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:721:27: sparse: struct dma_fence_ops const *
include/linux/dma-fence.h:732:27: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/dma-fence.h:732:27: sparse: struct dma_fence_ops const [noderef] __rcu *
include/linux/dma-fence.h:732:27: sparse: struct dma_fence_ops const *
--
drivers/dma-buf/dma-fence.c:1043:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *timeline @@ got char * @@
drivers/dma-buf/dma-fence.c:1043:38: sparse: expected char const [noderef] __rcu *timeline
drivers/dma-buf/dma-fence.c:1043:38: sparse: got char *
drivers/dma-buf/dma-fence.c:1044:36: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *driver @@ got char * @@
drivers/dma-buf/dma-fence.c:1044:36: sparse: expected char const [noderef] __rcu *driver
drivers/dma-buf/dma-fence.c:1044:36: sparse: got char *
drivers/dma-buf/dma-fence.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/dma_fence.h):
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
>> include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
vim +721 include/linux/dma-fence.h
976b6d97c62347 Christian König 2022-01-19 712
976b6d97c62347 Christian König 2022-01-19 713 /**
976b6d97c62347 Christian König 2022-01-19 714 * dma_fence_is_array - check if a fence is from the array subclass
976b6d97c62347 Christian König 2022-01-19 715 * @fence: the fence to test
976b6d97c62347 Christian König 2022-01-19 716 *
976b6d97c62347 Christian König 2022-01-19 717 * Return true if it is a dma_fence_array and false otherwise.
976b6d97c62347 Christian König 2022-01-19 718 */
976b6d97c62347 Christian König 2022-01-19 719 static inline bool dma_fence_is_array(struct dma_fence *fence)
976b6d97c62347 Christian König 2022-01-19 720 {
976b6d97c62347 Christian König 2022-01-19 @721 return fence->ops == &dma_fence_array_ops;
976b6d97c62347 Christian König 2022-01-19 722 }
976b6d97c62347 Christian König 2022-01-19 723
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-21 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260219160822.1529-1-christian.koenig@amd.com>
2026-02-19 16:07 ` [PATCH 1/8] dma-buf: protected fence ops by RCU v7 Christian König
2026-02-21 14:15 ` kernel test robot [this message]
2026-02-21 14:26 ` kernel test robot
2026-02-19 16:07 ` [PATCH 2/8] dma-buf: detach fence ops on signal v2 Christian König
2026-02-21 15:28 ` kernel test robot
2026-02-19 16:07 ` [PATCH 3/8] dma-buf: abstract fence locking v2 Christian König
2026-02-19 16:07 ` [PATCH 4/8] dma-buf: inline spinlock for fence protection v5 Christian König
2026-02-19 16:07 ` [PATCH 5/8] dma-buf/selftests: test RCU ops and inline lock v2 Christian König
2026-02-19 16:07 ` [PATCH 6/8] dma-buf: use inline lock for the stub fence v2 Christian König
2026-02-19 16:07 ` [PATCH 7/8] dma-buf: use inline lock for the dma-fence-array Christian König
2026-02-19 16:07 ` [PATCH 8/8] dma-buf: use inline lock for the dma-fence-chain Christian König
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=202602212248.xPSr8tt8-lkp@intel.com \
--to=lkp@intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=matthew.brost@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=phasta@mailbox.org \
--cc=sumit.semwal@linaro.org \
/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