From: kernel test robot <lkp@intel.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-hyperv@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Juergen Gross <jgross@suse.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
Waiman Long <longman@redhat.com>, Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 01/21] x86/paravirt: Remove not needed includes of paravirt.h
Date: Thu, 18 Sep 2025 11:18:00 +0800 [thread overview]
Message-ID: <202509181151.ja2As5H4-lkp@intel.com> (raw)
In-Reply-To: <20250917145220.31064-2-jgross@suse.com>
Hi Juergen,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on kvm/queue kvm/next linus/master v6.17-rc6 next-20250917]
[cannot apply to tip/x86/core kvm/linux-next]
[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/Juergen-Gross/x86-paravirt-Remove-not-needed-includes-of-paravirt-h/20250917-230321
base: tip/sched/core
patch link: https://lore.kernel.org/r/20250917145220.31064-2-jgross%40suse.com
patch subject: [PATCH v2 01/21] x86/paravirt: Remove not needed includes of paravirt.h
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20250918/202509181151.ja2As5H4-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250918/202509181151.ja2As5H4-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/202509181151.ja2As5H4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/cpu.c:13:
In file included from include/linux/sched/isolation.h:5:
In file included from include/linux/cpuset.h:18:
In file included from include/linux/mmu_context.h:5:
>> arch/x86/include/asm/mmu_context.h:225:2: error: call to undeclared function 'paravirt_enter_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
225 | paravirt_enter_mmap(mm);
| ^
>> arch/x86/include/asm/mmu_context.h:232:2: error: call to undeclared function 'paravirt_arch_exit_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
232 | paravirt_arch_exit_mmap(mm);
| ^
arch/x86/include/asm/mmu_context.h:232:2: note: did you mean 'ldt_arch_exit_mmap'?
arch/x86/include/asm/mmu_context.h:61:6: note: 'ldt_arch_exit_mmap' declared here
61 | void ldt_arch_exit_mmap(struct mm_struct *mm);
| ^
In file included from kernel/cpu.c:42:
In file included from include/trace/events/power.h:12:
In file included from include/linux/trace_events.h:10:
In file included from include/linux/perf_event.h:53:
In file included from include/linux/security.h:35:
In file included from include/linux/bpf.h:33:
In file included from arch/x86/include/asm/rqspinlock.h:5:
arch/x86/include/asm/paravirt.h:736:20: error: static declaration of 'paravirt_enter_mmap' follows non-static declaration
736 | static inline void paravirt_enter_mmap(struct mm_struct *mm)
| ^
arch/x86/include/asm/mmu_context.h:225:2: note: previous implicit declaration is here
225 | paravirt_enter_mmap(mm);
| ^
In file included from kernel/cpu.c:42:
In file included from include/trace/events/power.h:12:
In file included from include/linux/trace_events.h:10:
In file included from include/linux/perf_event.h:53:
In file included from include/linux/security.h:35:
In file included from include/linux/bpf.h:33:
In file included from arch/x86/include/asm/rqspinlock.h:5:
arch/x86/include/asm/paravirt.h:742:20: error: static declaration of 'paravirt_arch_exit_mmap' follows non-static declaration
742 | static inline void paravirt_arch_exit_mmap(struct mm_struct *mm)
| ^
arch/x86/include/asm/mmu_context.h:232:2: note: previous implicit declaration is here
232 | paravirt_arch_exit_mmap(mm);
| ^
4 errors generated.
--
In file included from kernel/workqueue.c:52:
In file included from include/linux/sched/isolation.h:5:
In file included from include/linux/cpuset.h:18:
In file included from include/linux/mmu_context.h:5:
>> arch/x86/include/asm/mmu_context.h:225:2: error: call to undeclared function 'paravirt_enter_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
225 | paravirt_enter_mmap(mm);
| ^
>> arch/x86/include/asm/mmu_context.h:232:2: error: call to undeclared function 'paravirt_arch_exit_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
232 | paravirt_arch_exit_mmap(mm);
| ^
arch/x86/include/asm/mmu_context.h:232:2: note: did you mean 'ldt_arch_exit_mmap'?
arch/x86/include/asm/mmu_context.h:61:6: note: 'ldt_arch_exit_mmap' declared here
61 | void ldt_arch_exit_mmap(struct mm_struct *mm);
| ^
2 errors generated.
--
>> arch/x86/kernel/x86_init.c:90:15: error: use of undeclared identifier 'default_banner'
90 | .banner = default_banner,
| ^
1 error generated.
--
In file included from arch/x86/mm/init.c:30:
>> arch/x86/include/asm/mmu_context.h:225:2: error: call to undeclared function 'paravirt_enter_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
225 | paravirt_enter_mmap(mm);
| ^
>> arch/x86/include/asm/mmu_context.h:232:2: error: call to undeclared function 'paravirt_arch_exit_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
232 | paravirt_arch_exit_mmap(mm);
| ^
arch/x86/include/asm/mmu_context.h:232:2: note: did you mean 'ldt_arch_exit_mmap'?
arch/x86/include/asm/mmu_context.h:61:6: note: 'ldt_arch_exit_mmap' declared here
61 | void ldt_arch_exit_mmap(struct mm_struct *mm);
| ^
>> arch/x86/mm/init.c:827:2: error: call to undeclared function 'paravirt_enter_mmap'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
827 | paravirt_enter_mmap(text_poke_mm);
| ^
3 errors generated.
vim +/paravirt_enter_mmap +225 arch/x86/include/asm/mmu_context.h
a31e184e4f6996 Dave Hansen 2019-01-02 221
c10e83f598d080 Thomas Gleixner 2017-12-14 222 static inline int arch_dup_mmap(struct mm_struct *oldmm, struct mm_struct *mm)
a1ea1c032b8f8c Dave Hansen 2014-11-18 223 {
a31e184e4f6996 Dave Hansen 2019-01-02 224 arch_dup_pkeys(oldmm, mm);
c9ae1b10d95610 Juergen Gross 2023-02-07 @225 paravirt_enter_mmap(mm);
82721d8b25d76c Kirill A. Shutemov 2023-03-12 226 dup_lam(oldmm, mm);
a4828f81037f49 Thomas Gleixner 2017-12-14 227 return ldt_dup_context(oldmm, mm);
a1ea1c032b8f8c Dave Hansen 2014-11-18 228 }
a1ea1c032b8f8c Dave Hansen 2014-11-18 229
a1ea1c032b8f8c Dave Hansen 2014-11-18 230 static inline void arch_exit_mmap(struct mm_struct *mm)
a1ea1c032b8f8c Dave Hansen 2014-11-18 231 {
a1ea1c032b8f8c Dave Hansen 2014-11-18 @232 paravirt_arch_exit_mmap(mm);
f55f0501cbf65e Andy Lutomirski 2017-12-12 233 ldt_arch_exit_mmap(mm);
a1ea1c032b8f8c Dave Hansen 2014-11-18 234 }
a1ea1c032b8f8c Dave Hansen 2014-11-18 235
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-18 3:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 14:51 [PATCH v2 00/21] paravirt: cleanup and reorg Juergen Gross
2025-09-17 14:52 ` [PATCH v2 01/21] x86/paravirt: Remove not needed includes of paravirt.h Juergen Gross
2025-09-18 3:18 ` kernel test robot [this message]
2025-09-17 14:52 ` [PATCH v2 12/21] x86/paravirt: Move paravirt_sched_clock() related code into tsc.c Juergen Gross
2025-09-17 14:52 ` [PATCH v2 21/21] x86/pvlocks: Move paravirt spinlock functions into own header Juergen Gross
2025-09-18 2:45 ` kernel test robot
2025-09-18 5:56 ` Juergen Gross
2025-09-18 5:38 ` kernel test robot
2026-02-20 4:10 ` [PATCH v2 00/21] paravirt: cleanup and reorg patchwork-bot+linux-riscv
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=202509181151.ja2As5H4-lkp@intel.com \
--to=lkp@intel.com \
--cc=boqun.feng@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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