From: kernel test robot <lkp@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Dave Airlie <airlied@redhat.com>
Subject: include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression
Date: Sat, 12 Sep 2026 03:12:37 +0800 [thread overview]
Message-ID: <202609120233.6Elxc35n-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 08df884136f1c1197bab2a27814404fd329d9aac
commit: 21f6bcdf2be72e750dbe430b7227a66763a58466 Merge tag 'drm-misc-next-2026-02-26' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-next
date: 6 months ago
config: microblaze-randconfig-r112-20260910 (https://download.01.org/0day-ci/archive/20260912/202609120233.6Elxc35n-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260912/202609120233.6Elxc35n-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: 21f6bcdf2be7 ("Merge tag 'drm-misc-next-2026-02-26' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-next")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609120233.6Elxc35n-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/dma-buf/dma-fence.c:1040:38: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *timeline @@ got char * @@
drivers/dma-buf/dma-fence.c:1040:38: sparse: expected char const [noderef] __rcu *timeline
drivers/dma-buf/dma-fence.c:1040:38: sparse: got char *
drivers/dma-buf/dma-fence.c:1041:36: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected char const [noderef] __rcu *driver @@ got char * @@
drivers/dma-buf/dma-fence.c:1041:36: sparse: expected char const [noderef] __rcu *driver
drivers/dma-buf/dma-fence.c:1041: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 +17 include/trace/events/dma_fence.h
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 11
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 12 /*
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 13 * Safe only for call sites which are guaranteed to not race with fence
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 14 * signaling,holding the fence->lock and having checked for not signaled, or the
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 15 * signaling path itself.
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 16 */
62918542b7bf08 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-16 @17 DECLARE_EVENT_CLASS(dma_fence,
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 18
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 19 TP_PROTO(struct dma_fence *fence),
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 20
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 21 TP_ARGS(fence),
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 22
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 23 TP_STRUCT__entry(
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 24 __string(driver, fence->ops->get_driver_name(fence))
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 25 __string(timeline, fence->ops->get_timeline_name(fence))
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 26 __field(unsigned int, context)
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 27 __field(unsigned int, seqno)
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 28 ),
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 29
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 30 TP_fast_assign(
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 31 __assign_str(driver);
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 32 __assign_str(timeline);
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 33 __entry->context = fence->context;
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 34 __entry->seqno = fence->seqno;
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 35 ),
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 36
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 37 TP_printk("driver=%s timeline=%s context=%u seqno=%u",
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 38 __get_str(driver), __get_str(timeline), __entry->context,
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 39 __entry->seqno)
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 40 );
506aa8b02a8d68 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-06-10 41
:::::: The code at line 17 was first introduced by commit
:::::: 62918542b7bf08860a60ebbde7654486e0ac0776 dma-fence: Fix sparse warnings due __rcu annotations
:::::: TO: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
:::::: CC: Christian König <christian.koenig@amd.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-11 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 19:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-12 8:46 include/trace/events/dma_fence.h:17:1: sparse: sparse: dereference of noderef expression kernel test robot
2026-06-02 6:32 kernel test robot
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=202609120233.6Elxc35n-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.brost@intel.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.