From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@lists.01.org, Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:tglx/devel/depthtracking 44/45] arch/x86/lib/putuser.S:81: Error: symbol `__put_user_nocheck_2' is already defined
Date: Thu, 21 Jul 2022 20:12:49 +0800 [thread overview]
Message-ID: <202207212007.ELVbSv77-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block tglx/devel/depthtracking
head: 714d29e3e7e3faac27142424ae2533163ddd3a46
commit: 825ec2afef752357059c356cf19e8cd6230af560 [44/45] x86/putuser: Provide room for padding
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220721/202207212007.ELVbSv77-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/ammarfaizi2/linux-block/commit/825ec2afef752357059c356cf19e8cd6230af560
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block tglx/devel/depthtracking
git checkout 825ec2afef752357059c356cf19e8cd6230af560
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86/lib/putuser.S: Assembler messages:
>> arch/x86/lib/putuser.S:81: Error: symbol `__put_user_nocheck_2' is already defined
vim +81 arch/x86/lib/putuser.S
79
80 SYM_FUNC_START(__put_user_nocheck_2)
> 81 SYM_INNER_LABEL(__put_user_nocheck_2, SYM_L_GLOBAL)
82 ENDBR
83 ASM_STAC
84 2: movw %ax,(%_ASM_CX)
85 xor %ecx,%ecx
86 ASM_CLAC
87 RET
88 SYM_FUNC_END(__put_user_nocheck_2)
89 EXPORT_SYMBOL(__put_user_nocheck_2)
90
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-21 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202207212007.ELVbSv77-lkp@intel.com \
--to=lkp@intel.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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