mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/powerpc/kernel/entry_64.S:241: Error: operand out of range (0xfe10 is not between 0xffffffffffff8000 and 0x7fff)
Date: Mon, 5 Feb 2024 00:56:01 +0800	[thread overview]
Message-ID: <202402050021.ZyajE6BS-lkp@intel.com> (raw)

Hi Michael,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478
commit: 3e8635fb2e072672cbc650989ffedf8300ad67fb powerpc/kasan: Force thread size increase with KASAN
date:   1 year, 8 months ago
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20240205/202402050021.ZyajE6BS-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240205/202402050021.ZyajE6BS-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/202402050021.ZyajE6BS-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/powerpc/kernel/entry_64.S: Assembler messages:
>> arch/powerpc/kernel/entry_64.S:241: Error: operand out of range (0xfe10 is not between 0xffffffffffff8000 and 0x7fff)
--
   {standard input}: Assembler messages:
>> {standard input}:7739: Error: operand out of range (0xff90 is not between 0xffffffffffff8000 and 0x7ffc)
   {standard input}:9318: Error: operand out of range (0xff90 is not between 0xffffffffffff8000 and 0x7ffc)
--
   arch/powerpc/kernel/misc_64.S: Assembler messages:
>> arch/powerpc/kernel/misc_64.S:387: Error: operand out of range (0xff90 is not between 0xffffffffffff8000 and 0x7ffc)
--
   arch/powerpc/kvm/book3s_hv_rmhandlers.S: Assembler messages:
>> arch/powerpc/kvm/book3s_hv_rmhandlers.S:2689: Error: operand out of range (0x8310 is not between 0xffffffffffff8001 and 0x8000)


vim +241 arch/powerpc/kernel/entry_64.S

2d27cfd3286966 Benjamin Herrenschmidt 2009-07-23  236  
7306e83ccf5ce3 Christophe Leroy       2019-01-17  237  	clrrdi	r7, r8, THREAD_SHIFT	/* base of new stack */
9994a33865f4d5 Paul Mackerras         2005-10-10  238  	/* Note: this uses SWITCH_FRAME_SIZE rather than INT_FRAME_SIZE
9994a33865f4d5 Paul Mackerras         2005-10-10  239  	   because we don't need to leave the 288-byte ABI gap at the
9994a33865f4d5 Paul Mackerras         2005-10-10  240  	   top of the kernel stack. */
9994a33865f4d5 Paul Mackerras         2005-10-10 @241  	addi	r7,r7,THREAD_SIZE-SWITCH_FRAME_SIZE
9994a33865f4d5 Paul Mackerras         2005-10-10  242  
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  243  	/*
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  244  	 * PMU interrupts in radix may come in here. They will use r1, not
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  245  	 * PACAKSAVE, so this stack switch will not cause a problem. They
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  246  	 * will store to the process stack, which may then be migrated to
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  247  	 * another CPU. However the rq lock release on this CPU paired with
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  248  	 * the rq lock acquire on the new CPU before the stack becomes
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  249  	 * active on the new CPU, will order those stores.
e4c0fc5f72bca1 Nicholas Piggin        2017-06-09  250  	 */
9994a33865f4d5 Paul Mackerras         2005-10-10  251  	mr	r1,r8		/* start using new stack pointer */
9994a33865f4d5 Paul Mackerras         2005-10-10  252  	std	r7,PACAKSAVE(r13)
9994a33865f4d5 Paul Mackerras         2005-10-10  253  
714332858bfd40 Anton Blanchard        2012-09-03  254  	ld	r6,_CCR(r1)
714332858bfd40 Anton Blanchard        2012-09-03  255  	mtcrf	0xFF,r6
714332858bfd40 Anton Blanchard        2012-09-03  256  
9994a33865f4d5 Paul Mackerras         2005-10-10  257  	/* r3-r13 are destroyed -- Cort */
5290ae2b8e5fec Jordan Niethe          2019-12-11  258  	REST_NVGPRS(r1)
9994a33865f4d5 Paul Mackerras         2005-10-10  259  
9994a33865f4d5 Paul Mackerras         2005-10-10  260  	/* convert old thread to its task_struct for return value */
9994a33865f4d5 Paul Mackerras         2005-10-10  261  	addi	r3,r3,-THREAD
9994a33865f4d5 Paul Mackerras         2005-10-10  262  	ld	r7,_NIP(r1)	/* Return to _switch caller in new task */
9994a33865f4d5 Paul Mackerras         2005-10-10  263  	mtlr	r7
9994a33865f4d5 Paul Mackerras         2005-10-10  264  	addi	r1,r1,SWITCH_FRAME_SIZE
9994a33865f4d5 Paul Mackerras         2005-10-10  265  	blr
9994a33865f4d5 Paul Mackerras         2005-10-10  266  

:::::: The code at line 241 was first introduced by commit
:::::: 9994a33865f4d55c44c9731c01e1f891543278de powerpc: Introduce entry_{32,64}.S, misc_{32,64}.S, systbl.S

:::::: TO: Paul Mackerras <paulus@samba.org>
:::::: CC: Paul Mackerras <paulus@samba.org>

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

                 reply	other threads:[~2024-02-04 16:56 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=202402050021.ZyajE6BS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --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

all inboxes | Powered by JetHome®