From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 03/11] unwind: Introduce SFrame user space unwinding
Date: Sat, 14 Sep 2024 16:12:26 +0800 [thread overview]
Message-ID: <202409141653.JlQG6bQS-lkp@intel.com> (raw)
In-Reply-To: <ca2e603ae3dcfa3e836162ed8c301fd4d9fd4058.1726268190.git.jpoimboe@kernel.org>
Hi Josh,
kernel test robot noticed the following build errors:
[auto build test ERROR on perf-tools-next/perf-tools-next]
[also build test ERROR on tip/perf/core perf-tools/perf-tools linus/master v6.11-rc7 next-20240913]
[cannot apply to acme/perf/core]
[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/Josh-Poimboeuf/unwind-Introduce-generic-user-space-unwinding-interface/20240914-070619
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/ca2e603ae3dcfa3e836162ed8c301fd4d9fd4058.1726268190.git.jpoimboe%40kernel.org
patch subject: [PATCH v2 03/11] unwind: Introduce SFrame user space unwinding
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20240914/202409141653.JlQG6bQS-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project bf684034844c660b778f0eba103582f582b710c9)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409141653.JlQG6bQS-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/202409141653.JlQG6bQS-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/init-mm.c:8:
In file included from include/linux/mman.h:5:
In file included from include/linux/mm.h:2232:
include/linux/vmstat.h:517:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
517 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> mm/init-mm.c:48:26: error: expected expression
48 | INIT_MM_CONTEXT(init_mm),
| ^
mm/init-mm.c:49:16: error: expected expression
49 | INIT_MM_SFRAME,
| ^
1 warning and 2 errors generated.
vim +48 mm/init-mm.c
22
23 /*
24 * For dynamically allocated mm_structs, there is a dynamically sized cpumask
25 * at the end of the structure, the size of which depends on the maximum CPU
26 * number the system can see. That way we allocate only as much memory for
27 * mm_cpumask() as needed for the hundreds, or thousands of processes that
28 * a system typically runs.
29 *
30 * Since there is only one init_mm in the entire system, keep it simple
31 * and size this cpu_bitmask to NR_CPUS.
32 */
33 struct mm_struct init_mm = {
34 .mm_mt = MTREE_INIT_EXT(mm_mt, MM_MT_FLAGS, init_mm.mmap_lock),
35 .pgd = swapper_pg_dir,
36 .mm_users = ATOMIC_INIT(2),
37 .mm_count = ATOMIC_INIT(1),
38 .write_protect_seq = SEQCNT_ZERO(init_mm.write_protect_seq),
39 MMAP_LOCK_INITIALIZER(init_mm)
40 .page_table_lock = __SPIN_LOCK_UNLOCKED(init_mm.page_table_lock),
41 .arg_lock = __SPIN_LOCK_UNLOCKED(init_mm.arg_lock),
42 .mmlist = LIST_HEAD_INIT(init_mm.mmlist),
43 #ifdef CONFIG_PER_VMA_LOCK
44 .mm_lock_seq = 0,
45 #endif
46 .user_ns = &init_user_ns,
47 .cpu_bitmap = CPU_BITS_NONE,
> 48 INIT_MM_CONTEXT(init_mm),
49 INIT_MM_SFRAME,
50 };
51
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-09-14 8:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ca2e603ae3dcfa3e836162ed8c301fd4d9fd4058.1726268190.git.jpoimboe@kernel.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=202409141653.JlQG6bQS-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox