From: Mike Rapoport <rppt@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [rppt:zero-page/v0 1/1] ERROR: modpost: vmlinux: 'empty_zero_page' exported twice. Previous export was in vmlinux
Date: Thu, 22 Jan 2026 11:17:02 +0200 [thread overview]
Message-ID: <aXHrDsAjeoT_8-vr@kernel.org> (raw)
In-Reply-To: <20260122051722.GC3770486@ax162>
On Wed, Jan 21, 2026 at 10:17:22PM -0700, Nathan Chancellor wrote:
> On Thu, Jan 22, 2026 at 11:14:04AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git zero-page/v0
> > head: 53d07913878ea27d6fe4224e8581729185291278
> > commit: 53d07913878ea27d6fe4224e8581729185291278 [1/1] dev: arch, mm: consolidate empty_zero_page
> > config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260122/202601221150.JsPp145b-lkp@intel.com/config)
> > compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260122/202601221150.JsPp145b-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/202601221150.JsPp145b-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>, old ones prefixed by <<):
> >
> > >> ERROR: modpost: vmlinux: 'empty_zero_page' exported twice. Previous export was in vmlinux
>
> Seems like the following should fix that?
>
> diff --git a/arch/hexagon/kernel/hexagon_ksyms.c b/arch/hexagon/kernel/hexagon_ksyms.c
> index 36a80e31d187..81bc6f81e200 100644
> --- a/arch/hexagon/kernel/hexagon_ksyms.c
> +++ b/arch/hexagon/kernel/hexagon_ksyms.c
> @@ -17,7 +17,6 @@ EXPORT_SYMBOL(raw_copy_to_user);
> EXPORT_SYMBOL(__vmgetie);
> EXPORT_SYMBOL(__vmsetie);
> EXPORT_SYMBOL(__vmyield);
> -EXPORT_SYMBOL(empty_zero_page);
> EXPORT_SYMBOL(memcpy);
> EXPORT_SYMBOL(memset);
Yes, it should :)
Thanks!
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-01-22 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 3:14 [rppt:zero-page/v0 1/1] ERROR: modpost: vmlinux: 'empty_zero_page' exported twice. Previous export was in vmlinux kernel test robot
2026-01-22 5:17 ` Nathan Chancellor
2026-01-22 9:17 ` Mike Rapoport [this message]
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=aXHrDsAjeoT_8-vr@kernel.org \
--to=rppt@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox