From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 03/11] unwind: Introduce SFrame user space unwinding
Date: Sat, 14 Sep 2024 15:40:38 +0800 [thread overview]
Message-ID: <202409141501.yaoIVdSI-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: alpha-allnoconfig (https://download.01.org/0day-ci/archive/20240914/202409141501.yaoIVdSI-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409141501.yaoIVdSI-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/202409141501.yaoIVdSI-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> mm/init-mm.c:48:33: error: expected expression before ',' token
48 | INIT_MM_CONTEXT(init_mm),
| ^
>> mm/init-mm.c:48:33: warning: excess elements in struct initializer
mm/init-mm.c:48:33: note: (near initialization for 'init_mm')
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
next prev parent reply other threads:[~2024-09-14 7:40 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 23:02 [PATCH v2 00/11] unwind, perf: sframe user space unwinding, deferred perf callchains Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 01/11] unwind: Introduce generic user space unwinding interface Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 02/11] unwind/x86: Add HAVE_USER_UNWIND Josh Poimboeuf
2024-09-14 14:07 ` kernel test robot
2024-09-15 12:18 ` Dan Carpenter
2024-09-16 11:46 ` Peter Zijlstra
2024-10-20 8:09 ` Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 03/11] unwind: Introduce SFrame user space unwinding Josh Poimboeuf
2024-09-14 7:40 ` kernel test robot [this message]
2024-09-14 8:12 ` kernel test robot
2024-09-14 11:23 ` Steven Rostedt
2024-10-01 18:20 ` Indu Bhagat
2024-10-01 18:36 ` Steven Rostedt
2024-10-02 8:18 ` Florian Weimer
2024-10-02 14:05 ` Steven Rostedt
2024-10-23 13:59 ` Jens Remus
2024-10-27 17:49 ` Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 04/11] unwind/x86/64: Add HAVE_USER_UNWIND_SFRAME Josh Poimboeuf
2024-09-14 16:25 ` kernel test robot
2024-09-15 12:20 ` Dan Carpenter
2024-09-13 23:02 ` [PATCH v2 05/11] perf/x86: Use user_unwind interface Josh Poimboeuf
2024-09-16 6:48 ` kernel test robot
2024-09-17 22:01 ` Namhyung Kim
2024-09-13 23:02 ` [PATCH v2 06/11] perf: Remove get_perf_callchain() 'init_nr' argument Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 07/11] perf: Remove get_perf_callchain() 'crosstask' argument Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 08/11] perf: Simplify get_perf_callchain() user logic Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 09/11] perf: Introduce deferred user callchains Josh Poimboeuf
2024-09-14 8:22 ` kernel test robot
2024-09-17 22:07 ` Namhyung Kim
2024-09-13 23:02 ` [PATCH v2 10/11] perf/x86: Add HAVE_PERF_CALLCHAIN_DEFERRED Josh Poimboeuf
2024-09-13 23:02 ` [PATCH v2 11/11] perf/x86: Enable SFrame unwinding for deferred user callchains Josh Poimboeuf
2024-09-14 12:12 ` [PATCH v2 00/11] unwind, perf: sframe user space unwinding, deferred perf callchains Steven Rostedt
2024-09-15 11:11 ` Josh Poimboeuf
2024-09-15 11:38 ` Steven Rostedt
2024-09-16 14:08 ` Peter Zijlstra
2024-09-16 15:39 ` Josh Poimboeuf
2024-09-16 18:15 ` Peter Zijlstra
2024-09-16 0:15 ` Mathieu Desnoyers
2024-09-16 0:33 ` Mathieu Desnoyers
2024-09-17 0:37 ` Mathieu Desnoyers
2024-09-16 22:46 ` Steven Rostedt
2024-09-17 21:58 ` Namhyung Kim
2024-09-18 5:14 ` Mathieu Desnoyers
2024-10-03 2:31 ` Steven Rostedt
2024-10-03 2:37 ` Josh Poimboeuf
2024-10-03 14:56 ` Steven Rostedt
2024-09-16 16:03 ` Steven Rostedt
2024-09-14 19:37 ` Namhyung Kim
2024-10-23 13:22 ` Jens Remus
2024-10-24 2:22 ` Steven Rostedt
2024-10-27 17:24 ` Josh Poimboeuf
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=202409141501.yaoIVdSI-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--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.