From: kernel test robot <lkp@intel.com>
To: greearb@candelatech.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH/RFC] debugobjects/slub: Print slab info and backtrace.
Date: Fri, 3 Nov 2023 15:42:10 +0800 [thread overview]
Message-ID: <202311031516.58fWVP0y-lkp@intel.com> (raw)
In-Reply-To: <20231103013704.1232723-1-greearb@candelatech.com>
Hi,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on vbabka-slab/for-next]
[also build test ERROR on tip/core/debugobjects linus/master v6.6 next-20231103]
[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/greearb-candelatech-com/debugobjects-slub-Print-slab-info-and-backtrace/20231103-093945
base: git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git for-next
patch link: https://lore.kernel.org/r/20231103013704.1232723-1-greearb%40candelatech.com
patch subject: [PATCH/RFC] debugobjects/slub: Print slab info and backtrace.
config: arc-randconfig-001-20231103 (https://download.01.org/0day-ci/archive/20231103/202311031516.58fWVP0y-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231103/202311031516.58fWVP0y-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/202311031516.58fWVP0y-lkp@intel.com/
All errors (new ones prefixed by >>):
lib/debugobjects.c: In function 'set_track_prepare':
>> lib/debugobjects.c:237:22: error: implicit declaration of function 'stack_trace_save'; did you mean 'stack_depot_save'? [-Werror=implicit-function-declaration]
237 | nr_entries = stack_trace_save(entries, ARRAY_SIZE(entries), 3);
| ^~~~~~~~~~~~~~~~
| stack_depot_save
cc1: some warnings being treated as errors
vim +237 lib/debugobjects.c
230
231 static noinline depot_stack_handle_t set_track_prepare(void)
232 {
233 depot_stack_handle_t trace_handle;
234 unsigned long entries[DEBUG_OBJ_ADDRS_COUNT];
235 unsigned int nr_entries;
236
> 237 nr_entries = stack_trace_save(entries, ARRAY_SIZE(entries), 3);
238 trace_handle = stack_depot_save(entries, nr_entries, GFP_NOWAIT);
239
240 return trace_handle;
241 }
242
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-03 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 1:37 [PATCH/RFC] debugobjects/slub: Print slab info and backtrace greearb
2023-11-03 1:49 ` Ben Greear
2023-11-05 16:20 ` Thomas Gleixner
2023-11-05 17:40 ` Ben Greear
2023-11-06 0:13 ` Thomas Gleixner
2023-11-03 7:42 ` kernel test robot [this message]
2023-11-03 10:25 ` kernel test robot
2023-11-03 13:02 ` kernel test robot
2023-11-05 9:35 ` Thomas Gleixner
2023-11-09 5:19 ` 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=202311031516.58fWVP0y-lkp@intel.com \
--to=lkp@intel.com \
--cc=greearb@candelatech.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.