LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	Saket Kumar Bhaskar <skb99@linux.ibm.com>
Cc: mpe@ellerman.id.au, npiggin@gmail.com, chleroy@kernel.org,
	segher@kernel.crashing.org, hbathini@linux.ibm.com,
	venkat88@linux.ibm.com, yeswanth@linux.ibm.com
Subject: Re: [PATCH v3] powerpc/irq: Fix missing r2 clobber in PCREL inline assembly
Date: Thu,  6 Aug 2026 09:46:35 +0530	[thread overview]
Message-ID: <178598971878.942627.14667171310466300671.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <10fc2cda485cd22e209a31d786bed1984bdf3982.1785732393.git.skb99@linux.ibm.com>

On Mon, 03 Aug 2026 10:58:43 +0530, Saket Kumar Bhaskar wrote:
> 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.
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/irq: Fix missing r2 clobber in PCREL inline assembly
      https://git.kernel.org/powerpc/c/00be69070d91d2be978e752bb117a0a4db0e1281

cheers


      parent reply	other threads:[~2026-08-06  4:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  5:28 [PATCH v3] powerpc/irq: Fix missing r2 clobber in PCREL inline assembly Saket Kumar Bhaskar
2026-08-03  6:03 ` Hari Bathini
2026-08-06  4:16 ` Madhavan Srinivasan [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=178598971878.942627.14667171310466300671.b4-ty@linux.ibm.com \
    --to=maddy@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=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=segher@kernel.crashing.org \
    --cc=skb99@linux.ibm.com \
    --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