From: kernel test robot <lkp@intel.com>
To: Li Pengfei <ljdlns1987@gmail.com>,
rostedt@goodmis.org, mhiramat@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, mathieu.desnoyers@efficios.com,
mark.rutland@arm.com, corbet@lwn.net, skhan@linuxfoundation.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
zhangbo56@xiaomi.com, lipengfei28@xiaomi.com, lkp@intel.com
Subject: Re: [PATCH v8 2/5] tracing: Use the stackmap from the ftrace stack recording path
Date: Sun, 8 Nov 2026 06:35:01 +0800 [thread overview]
Message-ID: <202611080654.sqFxIlwl-lkp@intel.com> (raw)
In-Reply-To: <20261107055139.3138633-3-lipengfei28@xiaomi.com>
Hi Li,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4539944e515183668109bdf4d0c3d7d228383d88]
url: https://github.com/intel-lab-lkp/linux/commits/Li-Pengfei/tracing-Add-lock-free-stackmap-for-stack-trace-deduplication/20261107-135135
base: 4539944e515183668109bdf4d0c3d7d228383d88
patch link: https://lore.kernel.org/r/20261107055139.3138633-3-lipengfei28%40xiaomi.com
patch subject: [PATCH v8 2/5] tracing: Use the stackmap from the ftrace stack recording path
config: powerpc-randconfig-1001-20261108 (https://download.01.org/0day-ci/archive/20261108/202611080654.sqFxIlwl-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261108/202611080654.sqFxIlwl-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/202611080654.sqFxIlwl-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/rbtree.h:24,
from include/linux/mm_types.h:11,
from include/linux/mmzone.h:22,
from include/linux/gfp.h:7,
from include/linux/mm.h:8,
from include/linux/ring_buffer.h:5,
from kernel/trace/trace.c:15:
kernel/trace/trace.c: In function 'record_stackmap':
>> include/linux/rcupdate.h:502:9: error: dereferencing pointer to incomplete type 'struct ftrace_stackmap'
typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
^
include/linux/rcupdate.h:684:2: note: in expansion of macro '__rcu_dereference_check'
__rcu_dereference_check((p), __UNIQUE_ID(rcu), \
^~~~~~~~~~~~~~~~~~~~~~~
include/linux/rcupdate.h:758:34: note: in expansion of macro 'rcu_dereference_sched_check'
#define rcu_dereference_sched(p) rcu_dereference_sched_check(p, 0)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/trace/trace.c:2154:9: note: in expansion of macro 'rcu_dereference_sched'
smap = rcu_dereference_sched(tr->stackmap);
^~~~~~~~~~~~~~~~~~~~~
vim +502 include/linux/rcupdate.h
76c8eaafe4f061f Paul E. McKenney 2021-04-21 492
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 493 #define __rcu_access_pointer(p, local, space) \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 494 ({ \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 495 typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
423a86a610cad12 Joel Fernandes (Google 2018-12-12 496) rcu_check_sparse(p, space); \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 497 ((typeof(*p) __force __kernel *)(local)); \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 498 })
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 499 #define __rcu_dereference_check(p, local, c, space) \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 500 ({ \
ac59853c06993a4 Pranith Kumar 2014-11-13 501 /* Dependency order vs. p above. */ \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 @502 typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
f78f5b90c4ffa55 Paul E. McKenney 2015-06-18 503 RCU_LOCKDEP_WARN(!(c), "suspicious rcu_dereference_check() usage"); \
423a86a610cad12 Joel Fernandes (Google 2018-12-12 504) rcu_check_sparse(p, space); \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 505 ((typeof(*p) __force __kernel *)(local)); \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 506 })
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 507 #define __rcu_dereference_protected(p, local, c, space) \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 508 ({ \
f78f5b90c4ffa55 Paul E. McKenney 2015-06-18 509 RCU_LOCKDEP_WARN(!(c), "suspicious rcu_dereference_protected() usage"); \
423a86a610cad12 Joel Fernandes (Google 2018-12-12 510) rcu_check_sparse(p, space); \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 511 ((typeof(*p) __force __kernel *)(p)); \
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 512 })
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 513 #define __rcu_dereference_raw(p, local) \
995f1405610bd84 Paul E. McKenney 2016-07-01 514 ({ \
995f1405610bd84 Paul E. McKenney 2016-07-01 515 /* Dependency order vs. p above. */ \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 516 typeof(p) local = READ_ONCE(p); \
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 517 ((typeof(*p) __force __kernel *)(local)); \
995f1405610bd84 Paul E. McKenney 2016-07-01 518 })
24ba53017e188e0 Chun-Hung Tseng 2021-09-15 519 #define rcu_dereference_raw(p) __rcu_dereference_raw(p, __UNIQUE_ID(rcu))
ca5ecddfa8fcbd9 Paul E. McKenney 2010-04-28 520
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-11-07 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 5:51 [PATCH v8 0/5] tracing: Add stack trace deduplication for the ring buffer Li Pengfei
2026-11-07 5:51 ` [PATCH v8 1/5] tracing: Add lock-free stackmap for stack trace deduplication Li Pengfei
2026-11-07 5:51 ` [PATCH v8 2/5] tracing: Use the stackmap from the ftrace stack recording path Li Pengfei
2026-11-07 22:35 ` kernel test robot [this message]
2026-11-07 5:51 ` [PATCH v8 3/5] tracing: Add stackmap statistics interface Li Pengfei
[not found] ` <sashiko-outbox-202646@kernel.org>
2026-11-07 6:28 ` Li Pengfei
2026-11-07 5:51 ` [PATCH v8 4/5] Documentation: tracing: Document the ftrace stackmap Li Pengfei
2026-11-07 5:51 ` [PATCH v8 5/5] selftests/ftrace: Add a stackmap basic functionality test Li Pengfei
[not found] ` <sashiko-outbox-202648@kernel.org>
2026-11-07 6:28 ` Li Pengfei
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=202611080654.sqFxIlwl-lkp@intel.com \
--to=lkp@intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=ljdlns1987@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=zhangbo56@xiaomi.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®