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: Re: [PATCH v3 3/8] ring-buffer: Add ring_buffer_meta_scratch()
Date: Wed, 5 Mar 2025 12:02:59 +0800 [thread overview]
Message-ID: <202503051115.YJCV0nG8-lkp@intel.com> (raw)
In-Reply-To: <20250304012548.100322331@goodmis.org>
Hi Steven,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.14-rc5]
[cannot apply to trace/for-next next-20250304]
[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/ring-buffer-Use-kaslr-address-instead-of-text-delta/20250304-092821
base: linus/master
patch link: https://lore.kernel.org/r/20250304012548.100322331%40goodmis.org
patch subject: [PATCH v3 3/8] ring-buffer: Add ring_buffer_meta_scratch()
config: i386-buildonly-randconfig-002-20250305 (https://download.01.org/0day-ci/archive/20250305/202503051115.YJCV0nG8-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/20250305/202503051115.YJCV0nG8-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/202503051115.YJCV0nG8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/ring_buffer.c:2546: warning: Function parameter or struct member 'scratch_size' not described in '__ring_buffer_alloc_range'
kernel/trace/ring_buffer.c:2560: warning: Function parameter or struct member 'kaslr_addr' not described in 'ring_buffer_last_boot_delta'
kernel/trace/ring_buffer.c:2560: warning: Excess function parameter 'text' description in 'ring_buffer_last_boot_delta'
kernel/trace/ring_buffer.c:2560: warning: Excess function parameter 'data' description in 'ring_buffer_last_boot_delta'
vim +2546 kernel/trace/ring_buffer.c
7a8e76a3829f10 Steven Rostedt 2008-09-29 2526
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2527) /**
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2528) * __ring_buffer_alloc_range - allocate a new ring_buffer from existing memory
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2529) * @size: the size in bytes per cpu that is needed.
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2530) * @flags: attributes to set for the ring buffer.
0b60a7fb60b7d7 Julia Lawall 2024-09-30 2531 * @order: sub-buffer order
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2532) * @start: start of allocated range
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2533) * @range_size: size of allocated range
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2534) * @key: ring buffer reader_lock_key.
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2535) *
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2536) * Currently the only flag that is available is the RB_FL_OVERWRITE
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2537) * flag. This flag means that the buffer will overwrite old data
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2538) * when the buffer wraps. If this flag is not set, the buffer will
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2539) * drop data when the tail hits the head.
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2540) */
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2541) struct trace_buffer *__ring_buffer_alloc_range(unsigned long size, unsigned flags,
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2542) int order, unsigned long start,
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2543) unsigned long range_size,
56953131fbcf4d Steven Rostedt 2025-03-03 2544 unsigned long scratch_size,
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2545) struct lock_class_key *key)
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 @2546) {
56953131fbcf4d Steven Rostedt 2025-03-03 2547 return alloc_buffer(size, flags, order, start, start + range_size,
56953131fbcf4d Steven Rostedt 2025-03-03 2548 scratch_size, key);
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2549) }
be68d63a139bd4 Steven Rostedt (Google 2024-06-12 2550)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-03-05 4:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250304012548.100322331@goodmis.org>]
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=202503051115.YJCV0nG8-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