public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] tracing: Clean up use of trace_create_maxlat_file()
Date: Sun, 8 Feb 2026 17:29:36 +0800	[thread overview]
Message-ID: <202602081759.QQ7Yu6SK-lkp@intel.com> (raw)
In-Reply-To: <20260207191101.0e014abd@robin>

Hi Steven,

kernel test robot noticed the following build errors:

[auto build test ERROR on trace/for-next]
[also build test ERROR on linus/master v6.19-rc8 next-20260205]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/tracing-Clean-up-use-of-trace_create_maxlat_file/20260208-081407
base:   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link:    https://lore.kernel.org/r/20260207191101.0e014abd%40robin
patch subject: [PATCH] tracing: Clean up use of trace_create_maxlat_file()
config: arm-randconfig-r071-20260208 (https://download.01.org/0day-ci/archive/20260208/202602081759.QQ7Yu6SK-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
smatch version: v0.5.0-8994-gd50c5a4c
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260208/202602081759.QQ7Yu6SK-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/202602081759.QQ7Yu6SK-lkp@intel.com/

All errors (new ones prefixed by >>):

   kernel/trace/trace.c: In function 'trace_create_maxlat_file':
>> kernel/trace/trace.c:1967:13: error: 'struct trace_array' has no member named 'd_max_latency'; did you mean 'max_latency'?
    1967 |         tr->d_max_latency = trace_create_file("tracing_max_latency",
         |             ^~~~~~~~~~~~~
         |             max_latency


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

  parent reply	other threads:[~2026-02-08  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-08  0:11 [PATCH] tracing: Clean up use of trace_create_maxlat_file() Steven Rostedt
2026-02-08  0:11 ` [PATCH v3] " Steven Rostedt
2026-02-08  9:29 ` kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-06 17:12 [PATCH] " Steven Rostedt
2026-02-06 22:29 ` kernel test robot
2026-02-07  1:15 ` 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=202602081759.QQ7Yu6SK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --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