From: kernel test robot <lkp@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Christian König" <christian.koenig@amd.com>
Subject: include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Fri, 22 Aug 2025 18:26:31 +0800 [thread overview]
Message-ID: <202508221834.hekYlJqU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3957a5720157264dcc41415fbec7c51c4000fc2d
commit: 506aa8b02a8d6898c64cc095d233fbae1cef8b8a dma-fence: Add safe access helpers and document the rules
date: 2 months ago
config: sh-randconfig-r132-20250822 (https://download.01.org/0day-ci/archive/20250822/202508221834.hekYlJqU-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.1.0
reproduce: (https://download.01.org/0day-ci/archive/20250822/202508221834.hekYlJqU-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/202508221834.hekYlJqU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/dma-buf/dma-fence.c:1112:51: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected char const [noderef] __rcu * @@ got char const * @@
drivers/dma-buf/dma-fence.c:1112:51: sparse: expected char const [noderef] __rcu *
drivers/dma-buf/dma-fence.c:1112:51: sparse: got char const *
drivers/dma-buf/dma-fence.c:1114:24: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected char const [noderef] __rcu * @@ got char * @@
drivers/dma-buf/dma-fence.c:1114:24: sparse: expected char const [noderef] __rcu *
drivers/dma-buf/dma-fence.c:1114:24: sparse: got char *
drivers/dma-buf/dma-fence.c:1144:51: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected char const [noderef] __rcu * @@ got char const * @@
drivers/dma-buf/dma-fence.c:1144:51: sparse: expected char const [noderef] __rcu *
drivers/dma-buf/dma-fence.c:1144:51: sparse: got char const *
drivers/dma-buf/dma-fence.c:1146:24: sparse: sparse: incorrect type in return expression (different address spaces) @@ expected char const [noderef] __rcu * @@ got char * @@
drivers/dma-buf/dma-fence.c:1146:24: sparse: expected char const [noderef] __rcu *
drivers/dma-buf/dma-fence.c:1146:24: 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:12:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected char const *str @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected char const *str
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void const *driver_ptr_ @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected void const *driver_ptr_
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected char const *str @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected char const *str
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
>> include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void const *timeline_ptr_ @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected void const *timeline_ptr_
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected char const *str @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected char const *str
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void const *driver_ptr_ @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected void const *driver_ptr_
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected char const *str @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected char const *str
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
>> include/trace/events/dma_fence.h:12:1: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void const *timeline_ptr_ @@ got char const [noderef] __rcu * @@
include/trace/events/dma_fence.h:12:1: sparse: expected void const *timeline_ptr_
include/trace/events/dma_fence.h:12:1: sparse: got char const [noderef] __rcu *
vim +12 include/trace/events/dma_fence.h
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 11
f54d1867005c33 include/trace/events/dma_fence.h Chris Wilson 2016-10-25 @12 DECLARE_EVENT_CLASS(dma_fence,
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 13
f54d1867005c33 include/trace/events/dma_fence.h Chris Wilson 2016-10-25 14 TP_PROTO(struct dma_fence *fence),
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 15
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 16 TP_ARGS(fence),
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 17
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 18 TP_STRUCT__entry(
ecec875a6c3379 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-05-15 19 __string(driver, dma_fence_driver_name(fence))
ecec875a6c3379 include/trace/events/dma_fence.h Tvrtko Ursulin 2025-05-15 20 __string(timeline, dma_fence_timeline_name(fence))
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 21 __field(unsigned int, context)
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 22 __field(unsigned int, seqno)
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 23 ),
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 24
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 25 TP_fast_assign(
2c92ca849fcc6e include/trace/events/dma_fence.h Steven Rostedt (Google 2024-05-16 26) __assign_str(driver);
2c92ca849fcc6e include/trace/events/dma_fence.h Steven Rostedt (Google 2024-05-16 27) __assign_str(timeline);
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 28 __entry->context = fence->context;
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 29 __entry->seqno = fence->seqno;
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 30 ),
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 31
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 32 TP_printk("driver=%s timeline=%s context=%u seqno=%u",
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 33 __get_str(driver), __get_str(timeline), __entry->context,
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 34 __entry->seqno)
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 35 );
e941759c74a44d include/trace/events/fence.h Maarten Lankhorst 2014-07-01 36
:::::: The code at line 12 was first introduced by commit
:::::: f54d1867005c3323f5d8ad83eed823e84226c429 dma-buf: Rename struct fence to dma_fence
:::::: TO: Chris Wilson <chris@chris-wilson.co.uk>
:::::: CC: Daniel Vetter <daniel.vetter@ffwll.ch>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-22 10:26 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=202508221834.hekYlJqU-lkp@intel.com \
--to=lkp@intel.com \
--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
all inboxes | Powered by JetHome®