mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: John Stultz <jstultz@google.com>, LKML <linux-kernel@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, John Stultz <jstultz@google.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Alexander Potapenko <glider@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	kernel-team@android.com
Subject: Re: [PATCH v2 1/2] lib: stacklog_debug: Introduce helper tool for collecting and displaying stacktraces
Date: Sun, 17 Nov 2024 22:16:37 +0800	[thread overview]
Message-ID: <202411172216.8mrRZn7X-lkp@intel.com> (raw)
In-Reply-To: <20241116002322.1035417-1-jstultz@google.com>

Hi John,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-nonmm-unstable]
[also build test WARNING on linus/master v6.12-rc7 next-20241115]
[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/John-Stultz/lib-stackdepot-Avoid-null-pointer-if-stack_depot_save-is-called-too-early/20241116-230825
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
patch link:    https://lore.kernel.org/r/20241116002322.1035417-1-jstultz%40google.com
patch subject: [PATCH v2 1/2] lib: stacklog_debug: Introduce helper tool for collecting and displaying stacktraces
config: arm-randconfig-r132-20241117 (https://download.01.org/0day-ci/archive/20241117/202411172216.8mrRZn7X-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20241117/202411172216.8mrRZn7X-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/202411172216.8mrRZn7X-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> lib/stacklog_debug.c:19:1: sparse: sparse: symbol 'stack_lock' was not declared. Should it be static?
   lib/stacklog_debug.c:21:5: sparse: sparse: symbol 'head' was not declared. Should it be static?

vim +/stack_lock +19 lib/stacklog_debug.c

    17	
    18	#define LIST_ENTRIES 512
  > 19	DEFINE_SPINLOCK(stack_lock);
    20	depot_stack_handle_t stack_list[LIST_ENTRIES];
    21	int head, tail;
    22	

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

      parent reply	other threads:[~2024-11-17 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16  0:23 John Stultz
2024-11-16  0:23 ` [PATCH v2 2/2] lib: stackdepot: Avoid null pointer if stack_depot_save is called too early John Stultz
2024-11-17 14:16 ` kernel test robot [this message]

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=202411172216.8mrRZn7X-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=glider@google.com \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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

all inboxes | Powered by JetHome®