From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jpoimboe:static-key-deprecated 1/18] kernel/trace/trace_events_hist.c:825:36: error: no member named 'enabled' in 'struct static_key_false'
Date: Fri, 4 Oct 2024 04:01:06 +0800 [thread overview]
Message-ID: <202410040337.AVKyOkE0-lkp@intel.com> (raw)
Hi Josh,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git static-key-deprecated
head: 02560a85ce2d5e66cd2b6f92bc5491f6fd199e02
commit: dcb3457da83c22aae3efcd93357f35c70645c4bb [1/18] tracepoints: Use new static branch API
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20241004/202410040337.AVKyOkE0-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241004/202410040337.AVKyOkE0-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/202410040337.AVKyOkE0-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace_events_hist.c:825:36: error: no member named 'enabled' in 'struct static_key_false'
825 | if (unlikely(atomic_read(&tp->key.enabled) > 0)) {
| ~~~~~~~ ^
include/linux/compiler.h:77:42: note: expanded from macro 'unlikely'
77 | # define unlikely(x) __builtin_expect(!!(x), 0)
| ^
1 error generated.
vim +825 kernel/trace/trace_events_hist.c
7bbab38d07f318 Masami Hiramatsu 2018-11-05 816
726721a51838e3 Tom Zanussi 2020-05-28 817 typedef void (*synth_probe_func_t) (void *__data, u64 *var_ref_vals,
726721a51838e3 Tom Zanussi 2020-05-28 818 unsigned int *var_ref_idx);
4b147936fa5096 Tom Zanussi 2018-01-15 819
726721a51838e3 Tom Zanussi 2020-05-28 820 static inline void trace_synth(struct synth_event *event, u64 *var_ref_vals,
726721a51838e3 Tom Zanussi 2020-05-28 821 unsigned int *var_ref_idx)
4b147936fa5096 Tom Zanussi 2018-01-15 822 {
726721a51838e3 Tom Zanussi 2020-05-28 823 struct tracepoint *tp = event->tp;
4b147936fa5096 Tom Zanussi 2018-01-15 824
726721a51838e3 Tom Zanussi 2020-05-28 @825 if (unlikely(atomic_read(&tp->key.enabled) > 0)) {
726721a51838e3 Tom Zanussi 2020-05-28 826 struct tracepoint_func *probe_func_ptr;
726721a51838e3 Tom Zanussi 2020-05-28 827 synth_probe_func_t probe_func;
726721a51838e3 Tom Zanussi 2020-05-28 828 void *__data;
17911ff38aa58d Steven Rostedt (VMware 2019-10-11 829)
726721a51838e3 Tom Zanussi 2020-05-28 830 if (!(cpu_online(raw_smp_processor_id())))
726721a51838e3 Tom Zanussi 2020-05-28 831 return;
4b147936fa5096 Tom Zanussi 2018-01-15 832
726721a51838e3 Tom Zanussi 2020-05-28 833 probe_func_ptr = rcu_dereference_sched((tp)->funcs);
726721a51838e3 Tom Zanussi 2020-05-28 834 if (probe_func_ptr) {
726721a51838e3 Tom Zanussi 2020-05-28 835 do {
726721a51838e3 Tom Zanussi 2020-05-28 836 probe_func = probe_func_ptr->func;
726721a51838e3 Tom Zanussi 2020-05-28 837 __data = probe_func_ptr->data;
726721a51838e3 Tom Zanussi 2020-05-28 838 probe_func(__data, var_ref_vals, var_ref_idx);
726721a51838e3 Tom Zanussi 2020-05-28 839 } while ((++probe_func_ptr)->func);
726721a51838e3 Tom Zanussi 2020-05-28 840 }
726721a51838e3 Tom Zanussi 2020-05-28 841 }
4b147936fa5096 Tom Zanussi 2018-01-15 842 }
4b147936fa5096 Tom Zanussi 2018-01-15 843
:::::: The code at line 825 was first introduced by commit
:::::: 726721a51838e3983023f906580722fc83f804ee tracing: Move synthetic events to a separate file
:::::: TO: Tom Zanussi <zanussi@kernel.org>
:::::: CC: Steven Rostedt (VMware) <rostedt@goodmis.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-03 20:01 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=202410040337.AVKyOkE0-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).