LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Saket Kumar Bhaskar <skb99@linux.ibm.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	segher@kernel.crashing.org, hbathini@linux.ibm.com,
	venkat88@linux.ibm.com, yeswanth@linux.ibm.com
Subject: Re: [PATCH v2] powerpc/irq: Fix missing r2 clobber in PCREL inline assembly
Date: Wed, 29 Jul 2026 22:17:15 +0530	[thread overview]
Message-ID: <amouk4Znfoqo6G7o@linux.ibm.com> (raw)
In-Reply-To: <63007c21-4783-4a98-9853-62b36b737df3@kernel.org>

On Mon, Jul 27, 2026 at 02:09:12PM +0200, Christophe Leroy (CS GROUP) wrote:
> 
Hi Christophe, thanks for reviewing.
> 
> Le 27/07/2026 à 12:58, Saket Kumar Bhaskar a écrit :
> > In CONFIG_PPC_KERNEL_PCREL mode, r2 is no longer reserved for the TOC
> > pointer and is available as a caller-saved register [0].
> > 
> > Both call_do_irq() and call_do_softirq() use inline assembly to call
> > functions with stack switching, but fail to list r2 in their clobber
> > lists. This causes the compiler to assume r2 is preserved across these
> > calls, leading to register corruption when the called functions
> > (__do_irq and __do_softirq) clobber r2.
> > 
> > As a result of this kernel crash during interrupt handling is seen and
> > the kernel fails to boot:
> > 
> > BUG: Unable to handle kernel data access on write at 0xc000000404697638
> > Faulting instruction address: 0xc0000000000181ec
> > Oops: Kernel access of bad area, sig: 11 [#1]
> > NIP [c0000000000181ec] __do_IRQ+0x6c/0xc0
> > 
> > With older GCC, the compiler would conservatively allocate
> > callee-saved registers (like r31) for values spanning function calls,
> > accidentally avoiding the bug:
> > 
> > <__do_IRQ>:
> > 00 00 00 60 	nop
> > a6 02 08 7c 	mflr    r0
> > f8 ff e1 fb 	std     r31,-8(r1)
> > f0 ff c1 fb 	std     r30,-16(r1)
> > 2d 03 10 06 	pla     r31,53297316
> > 
> > ...
> > 
> > 3d e8 ff 4b 	bl      c0000000000165ac <__do_irq>
> > 00 00 21 e8 	ld      r1,0(r1)
> > 28 00 4d e9 	ld      r10,40(r13)
> > 40 00 21 38 	addi    r1,r1,64
> > 2a f9 aa 7f 	stdx    r29,r10,r31
> > 
> > With newer GCC 14, the compiler uses r2 for such values, exposing the
> > missing clobber specification:
> > 
> > <__do_IRQ>:
> > 00 00 00 60     nop
> > a6 02 08 7c     mflr    r0
> > f0 ff c1 fb     std     r30,-16(r1)
> > f8 ff e1 fb     std     r31,-8(r1)
> > 29 02 10 06     pla     r2,36252592     # c0000000022aadc0 <__irq_regs>
> > 
> > ...
> > 
> > 85 dc ff 4b 	bl      c000000000015ee0 <__do_irq>
> > 00 00 21 e8 	ld      r1,0(r1)
> > 28 00 2d e9 	ld      r9,40(r13)
> > 30 00 21 38 	addi    r1,r1,48
> > 2a 11 c9 7f 	stdx    r30,r9,r2
> > 
> > Fix this by adding r2 to the clobber list for both call_do_irq() and
> > call_do_softirq() when CONFIG_PPC_KERNEL_PCREL is enabled.
> > 
> > [0]: https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg313226.html
> > 
> > Fixes: 7e3a68be42e1 ("powerpc/64: vmlinux support building with PCREL addresing")
> > Signed-off-by: Saket Kumar Bhaskar <skb99@linux.ibm.com>
> > ---
> > Changes since v1:
> > Addressed comments from Segher:
> > * Modified comments to "clobber may happen"
> > 
> > v1: https://lore.kernel.org/all/dc021f42afa10396052499cbeda1772e30b7ca64.1784530547.git.skb99@linux.ibm.com/
> > 
> >   arch/powerpc/kernel/irq.c | 14 ++++++++++++--
> >   1 file changed, 12 insertions(+), 2 deletions(-)
> > 
> > diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
> > index a0e8b998c9b5..b5343cfd6c9f 100644
> > --- a/arch/powerpc/kernel/irq.c
> > +++ b/arch/powerpc/kernel/irq.c
> > @@ -218,7 +218,12 @@ static __always_inline void call_do_softirq(const void *sp)
> >   		   [callee] "i" (__do_softirq)
> >   		 : // Clobbers
> >   		   "lr", "xer", "ctr", "memory", "cr0", "cr1", "cr5", "cr6",
> > -		   "cr7", "r0", "r3", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> > +		   "cr7", "r0",
> > +		  /* r2 may be clobbered by the callee when using the ELFv2 ABI */
> 
> Not sure the comment is correct. You get CONFIG_PPC64_ELF_ABI_V2 without
> CONFIG_PPC_KERNEL_PCREL.
> 
> Kconfig help presents CONFIG_PPC_KERNEL_PCREL as an ABI extension.
> 
So considering your comment and Segher's observation https://lore.kernel.org/all/al33jmn9PmMJwYlz@gate/
would be better to reword it as:
/* r2 may be clobbered by the callee when using PCREL mode in the ELFv2 ABI. */
> > +#ifdef CONFIG_PPC_KERNEL_PCREL
> > +		   "r2",
> > +#endif
> > +		   "r3", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> >   		   "r11", "r12"
> 
> To minimise number of small lines I'd prefer something like:
> 
> 		   "lr", "xer", "ctr", "memory", "cr0", "cr1", "cr5", "cr6", "cr7", "r0",
> #ifdef CONFIG_PPC_KERNEL_PCREL
> 		   "r2",
> #endif
> 		   "r3", "r4", "r5", "r6", "r7", "r8", "r9", "r10", "r11", "r12"
> 
> 
Noted
> >   	);
> >   }
> > @@ -276,7 +281,12 @@ static __always_inline void call_do_irq(struct pt_regs *regs, void *sp)
> >   		   [callee] "i" (__do_irq)
> >   		 : // Clobbers
> >   		   "lr", "xer", "ctr", "memory", "cr0", "cr1", "cr5", "cr6",
> > -		   "cr7", "r0", "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> > +		   "cr7", "r0",
> > +		  /* r2 may be clobbered by the callee when using the ELFv2 ABI */
> > +#ifdef CONFIG_PPC_KERNEL_PCREL
> > +		   "r2",
> > +#endif
> > +		   "r4", "r5", "r6", "r7", "r8", "r9", "r10",
> 
> Same
> 
Noted
> >   		   "r11", "r12"
> >   	);
> >   }
> 
> Reviewed-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
> 
> 
Thanks,
Saket


      reply	other threads:[~2026-07-29 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 10:58 [PATCH v2] powerpc/irq: Fix missing r2 clobber in PCREL inline assembly Saket Kumar Bhaskar
2026-07-27 12:09 ` Christophe Leroy (CS GROUP)
2026-07-29 16:47   ` Saket Kumar Bhaskar [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=amouk4Znfoqo6G7o@linux.ibm.com \
    --to=skb99@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=hbathini@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=segher@kernel.crashing.org \
    --cc=venkat88@linux.ibm.com \
    --cc=yeswanth@linux.ibm.com \
    /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