From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [trace:trace/for-next 27/40] kernel/trace/trace.c:1967:6: error: no member named 'd_max_latency' in 'struct trace_array'; did you mean 'max_latency'?
Date: Mon, 09 Feb 2026 21:21:27 +0800 [thread overview]
Message-ID: <202602092133.fTdojd95-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace trace/for-next
head: c4f1fe47b106e9200cbb1b8951bd75f036d53bd3
commit: ba73713da50e5c24499ca8941171593466ea34f7 [27/40] tracing: Clean up use of trace_create_maxlat_file()
config: arm64-randconfig-003-20260209 (https://download.01.org/0day-ci/archive/20260209/202602092133.fTdojd95-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260209/202602092133.fTdojd95-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/202602092133.fTdojd95-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/trace.c:1967:6: error: no member named 'd_max_latency' in 'struct trace_array'; did you mean 'max_latency'?
1967 | tr->d_max_latency = trace_create_file("tracing_max_latency",
| ^~~~~~~~~~~~~
| max_latency
kernel/trace/trace.h:348:17: note: 'max_latency' declared here
348 | unsigned long max_latency;
| ^
kernel/trace/trace.c:9789:23: warning: shift count is negative [-Wshift-count-negative]
9789 | !((1ULL << i) & TOP_LEVEL_TRACE_FLAGS)) {
| ^~~~~~~~~~~~~~~~~~~~~
kernel/trace/trace.c:523:9: note: expanded from macro 'TOP_LEVEL_TRACE_FLAGS'
523 | TRACE_ITER(PROF_TEXT_OFFSET) | FPROFILE_DEFAULT_FLAGS)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
kernel/trace/trace.h:1439:42: note: expanded from macro 'TRACE_ITER'
1439 | (TRACE_ITER_##flag##_BIT < 0 ? 0 : 1ULL << (TRACE_ITER_##flag##_BIT))
| ^ ~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning and 1 error generated.
vim +1967 kernel/trace/trace.c
1959
1960 static void trace_create_maxlat_file(struct trace_array *tr,
1961 struct dentry *d_tracer)
1962 {
1963 #ifdef LATENCY_FS_NOTIFY
1964 INIT_WORK(&tr->fsnotify_work, latency_fsnotify_workfn);
1965 init_irq_work(&tr->fsnotify_irqwork, latency_fsnotify_workfn_irq);
1966 #endif
> 1967 tr->d_max_latency = trace_create_file("tracing_max_latency",
1968 TRACE_MODE_WRITE,
1969 d_tracer, tr,
1970 &tracing_max_lat_fops);
1971 }
1972
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-09 13:22 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=202602092133.fTdojd95-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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