All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v3] futex: Introduce __vdso_robust_futex_unlock_u32 and __vdso_robust_pi_futex_try_unlock_u32
Date: Sat, 14 Mar 2026 05:46:19 +0800	[thread overview]
Message-ID: <202603140547.Wi2MxToc-lkp@intel.com> (raw)
In-Reply-To: <20260312181850.2156985-1-mathieu.desnoyers@efficios.com>

Hi Mathieu,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on tip/locking/core]
[also build test ERROR on linus/master v7.0-rc3 next-20260311]
[cannot apply to tip/x86/core tip/x86/vdso]
[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/Mathieu-Desnoyers/futex-Introduce-__vdso_robust_futex_unlock_u32-and-__vdso_robust_pi_futex_try_unlock_u32/20260313-201027
base:   tip/locking/core
patch link:    https://lore.kernel.org/r/20260312181850.2156985-1-mathieu.desnoyers%40efficios.com
patch subject: [RFC PATCH v3] futex: Introduce __vdso_robust_futex_unlock_u32 and __vdso_robust_pi_futex_try_unlock_u32
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20260314/202603140547.Wi2MxToc-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260314/202603140547.Wi2MxToc-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/202603140547.Wi2MxToc-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/sched.h:13,
                    from include/linux/percpu.h:12,
                    from arch/arm64/include/asm/arch_timer.h:18,
                    from arch/arm64/include/asm/timex.h:8,
                    from include/linux/timex.h:67,
                    from include/linux/time32.h:13,
                    from include/linux/time.h:60,
                    from include/linux/compat.h:10,
                    from kernel/futex/core.c:34:
   kernel/futex/core.c: In function 'handle_futex_death':
>> arch/arm64/include/asm/processor.h:384:43: error: implicit declaration of function 'task_stack_page'; did you mean 'task_stack_vm_area'? [-Wimplicit-function-declaration]
     384 |         ((struct pt_regs *)(THREAD_SIZE + task_stack_page(p)) - 1)
         |                                           ^~~~~~~~~~~~~~~
   kernel/futex/core.c:1148:38: note: in expansion of macro 'task_pt_regs'
    1148 |                 futex_vdso_exception(task_pt_regs(curr), &in_futex_vdso, &vdso_need_action);
         |                                      ^~~~~~~~~~~~


vim +384 arch/arm64/include/asm/processor.h

2f79d2fc391e4ba Peter Collingbourne 2021-03-18  378  
9cce7a435f89c9e Catalin Marinas     2012-03-05  379  /* Thread switching */
9cce7a435f89c9e Catalin Marinas     2012-03-05  380  extern struct task_struct *cpu_switch_to(struct task_struct *prev,
9cce7a435f89c9e Catalin Marinas     2012-03-05  381  					 struct task_struct *next);
9cce7a435f89c9e Catalin Marinas     2012-03-05  382  
9cce7a435f89c9e Catalin Marinas     2012-03-05  383  #define task_pt_regs(p) \
34be98f4944f990 Ard Biesheuvel      2017-07-20 @384  	((struct pt_regs *)(THREAD_SIZE + task_stack_page(p)) - 1)
9cce7a435f89c9e Catalin Marinas     2012-03-05  385  

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

  reply	other threads:[~2026-03-13 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12 18:18 [RFC PATCH v3] futex: Introduce __vdso_robust_futex_unlock_u32 and __vdso_robust_pi_futex_try_unlock_u32 Mathieu Desnoyers
2026-03-13 21:46 ` kernel test robot [this message]
2026-03-13 21:46 ` 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=202603140547.Wi2MxToc-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=mathieu.desnoyers@efficios.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.