public inbox for [email protected]
 help / color / mirror / Atom feed
From: "Chen, Rong A" <[email protected]>
To: [email protected], kernel test robot <[email protected]>
Cc: Frederic Weisbecker <[email protected]>,
	[email protected],
	GNU/Weeb Mailing List <[email protected]>,
	[email protected]
Subject: Re: [kbuild-all] Re: [ammarfaizi2-block:paulmck/linux-rcu/pmladek.2022.06.15a 123/140] xtensa-linux-ld: arch/xtensa/kernel/entry.o:undefined reference to `context_tracking_user_exit'
Date: Fri, 1 Jul 2022 18:15:50 +0800	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20220630230823.GD1790663@paulmck-ThinkPad-P17-Gen-1>



On 7/1/2022 7:08 AM, Paul E. McKenney wrote:
> On Fri, Jul 01, 2022 at 04:15:11AM +0800, kernel test robot wrote:
>> tree:   https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/pmladek.2022.06.15a
>> head:   0ba7324b44282870af740a5a121add62c7f5f730
>> commit: 9d16390cc0d00ae1100bca4f4adb0ae2906631ec [123/140] context_tracking: Take idle eqs entrypoints over RCU
>> config: xtensa-randconfig-r004-20220629 (https://download.01.org/0day-ci/archive/20220701/[email protected]/config)
>> compiler: xtensa-linux-gcc (GCC) 11.3.0
>> reproduce (this is a W=1 build):
>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>          chmod +x ~/bin/make.cross
>>          # https://github.com/ammarfaizi2/linux-block/commit/9d16390cc0d00ae1100bca4f4adb0ae2906631ec
>>          git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
>>          git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/pmladek.2022.06.15a
>>          git checkout 9d16390cc0d00ae1100bca4f4adb0ae2906631ec
>>          # save the config file
>>          mkdir build_dir && cp config build_dir/.config
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=xtensa SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag where applicable
>> Reported-by: kernel test robot <[email protected]>
> 
> This should be fixed in the current version of this commit:
> 
> 6a87dff9f33a ("context_tracking: Take idle eqs entrypoints over RCU")
> 
> Please let me know if this commit does not address the problem.
> 
> 							Thaxn, Paul


Hi Paul,

I have confirmed that there's no such issue on commit 6a87dff9f33a,
but I'm not sure the commit fixed the issue, I can't find the error on
parent commit 24a9c54182b3 too.

   $ git log --oneline -2 6a87dff9f33a
   6a87dff9f33af context_tracking: Take idle eqs entrypoints over RCU
   24a9c54182b37 context_tracking: Split user tracking Kconfig

Best Regards,
Rong Chen

> 
>> All errors (new ones prefixed by >>):
>>
>>>> xtensa-linux-ld: arch/xtensa/kernel/entry.o:(.text+0x0): undefined reference to `context_tracking_user_exit'
>>>> xtensa-linux-ld: arch/xtensa/kernel/entry.o:(.text+0xc): undefined reference to `context_tracking_user_enter'
>>     xtensa-linux-ld: arch/xtensa/kernel/entry.o: in function `common_exception':
>>     arch/xtensa/kernel/entry.S:459: undefined reference to `context_tracking_user_exit'
>>     xtensa-linux-ld: arch/xtensa/kernel/entry.o: in function `common_exception_return':
>>     arch/xtensa/kernel/entry.S:542: undefined reference to `context_tracking_user_enter'
>>
>> -- 
>> 0-DAY CI Kernel Test Service
>> https://01.org/lkp
> _______________________________________________
> kbuild-all mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 

  reply	other threads:[~2022-07-01 10:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 20:15 [ammarfaizi2-block:paulmck/linux-rcu/pmladek.2022.06.15a 123/140] xtensa-linux-ld: arch/xtensa/kernel/entry.o:undefined reference to `context_tracking_user_exit' kernel test robot
2022-06-30 23:08 ` Paul E. McKenney
2022-07-01 10:15   ` Chen, Rong A [this message]
2022-07-01 13:53     ` [kbuild-all] " Paul E. McKenney

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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