The Linux Kernel Mailing List
 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>,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free()
Date: Wed, 5 Aug 2026 09:22:15 +0800	[thread overview]
Message-ID: <202608050901.w9NoTLGg-lkp@intel.com> (raw)
In-Reply-To: <20260701174829.67ab8a33@gandalf.local.home>

Hi Steven,

kernel test robot noticed the following build warnings:

[auto build test WARNING on trace/for-next]
[also build test WARNING on linus/master v7.2-rc6 next-20260804]
[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-Cleanup-event_enable_trigger_parse-by-using-__free/20260805-073956
base:   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link:    https://lore.kernel.org/r/20260701174829.67ab8a33%40gandalf.local.home
patch subject: [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free()
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20260805/202608050901.w9NoTLGg-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260805/202608050901.w9NoTLGg-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/202608050901.w9NoTLGg-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/file.h:13,
                    from include/linux/kernel_read_file.h:5,
                    from include/linux/security.h:26,
                    from kernel/trace/trace_events_trigger.c:8:
   kernel/trace/trace_events_trigger.c: In function 'event_enable_trigger_parse':
>> include/linux/cleanup.h:228:22: warning: ignoring return value of '__must_check_fn' declared with attribute 'warn_unused_result' [-Wunused-result]
     228 |         ((typeof(p)) __must_check_fn((__force const volatile void *)__get_and_null(p, NULL)))
         |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   kernel/trace/trace_events_trigger.c:1842:9: note: in expansion of macro 'no_free_ptr'
    1842 |         no_free_ptr(enable_data);
         |         ^~~~~~~~~~~


vim +228 include/linux/cleanup.h

85be6d84244706 Peter Zijlstra 2023-08-15  226  
54da6a0924311c Peter Zijlstra 2023-05-26  227  #define no_free_ptr(p) \
366fef794bd2b7 Ilpo Järvinen  2025-03-10 @228  	((typeof(p)) __must_check_fn((__force const volatile void *)__get_and_null(p, NULL)))
54da6a0924311c Peter Zijlstra 2023-05-26  229  

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-08-05  1:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 21:48 [PATCH] tracing: Cleanup event_enable_trigger_parse() by using __free() Steven Rostedt
2026-07-01 22:41 ` Masami Hiramatsu
2026-07-02  9:58 ` Markus Elfring
2026-07-02 20:53   ` Steven Rostedt
2026-07-03  5:00     ` Markus Elfring
2026-07-03 15:42       ` Steven Rostedt
2026-07-03 18:37         ` Markus Elfring
2026-07-03 19:09           ` Steven Rostedt
2026-07-03 19:20             ` Markus Elfring
2026-07-03 19:33               ` Steven Rostedt
2026-07-02 11:58 ` [PATCH] " Markus Elfring
2026-08-05  1:22 ` kernel test robot [this message]
2026-08-05  6:21 ` kernel test robot
2026-08-06 17:13   ` Steven Rostedt

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=202608050901.w9NoTLGg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Markus.Elfring@web.de \
    --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