mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Danish Khateeb <danishkhateeb03@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Allen Pais <allen.lkml@gmail.com>,
	sparclinux@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] sparc64: kprobes: fix relbranch_fixup() for BPr, FBfcc and FBPfcc
Date: Fri, 25 Sep 2026 23:28:22 +0900	[thread overview]
Message-ID: <20260925232822.094082fd46fb3b02d9cfff10@kernel.org> (raw)
In-Reply-To: <20260923144909.414968-2-danishkhateeb03@gmail.com>

On Wed, 23 Sep 2026 09:49:07 -0500
Danish Khateeb <danishkhateeb03@gmail.com> wrote:

> A kprobe single-steps a copy of the probed instruction in
> p->ainsn.insn[]. When the copy is a taken PC-relative branch, its target
> is relative to the copy, and relbranch_fixup() moves it back to the
> probed code. It only recognizes call, BPcc and Bicc, though. For a taken
> BPr (brz, brnz, ...), FBfcc or FBPfcc it keeps the target as is, and the
> kernel continues at the copy's address plus the branch displacement.
> 
> GCC often starts a function with a BPr on an argument. For example,
> __se_sys_getcpu() begins with "brz,pn %o0". With a kprobe on it
> ("p:kprobes/kgetcpu __se_sys_getcpu" in kprobe_events), the first
> getcpu(NULL, NULL, NULL) crashes the kernel in QEMU sun4u:
> 
>   init(1): Kernel illegal instruction [#1]
>   TSTATE: 0000004411001603 TPC: fffff800048d63c0 TNPC: fffff8000492631c
>   Kernel panic - not syncing: Fatal exception
> 
> Add the missing branch formats. BPr is matched with bit 28 clear. The
> CBcond instructions of newer CPUs share its op2 value, but they have no
> delay slot, so a taken one never reaches the single-step breakpoint and
> this function.
> 

Sounds reasonable. From kprobes maintainer point of view:

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>


Thanks,

> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
> ---
>  arch/sparc/kernel/kprobes.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/sparc/kernel/kprobes.c b/arch/sparc/kernel/kprobes.c
> index 191bbaca9921..9a26c57c8d33 100644
> --- a/arch/sparc/kernel/kprobes.c
> +++ b/arch/sparc/kernel/kprobes.c
> @@ -207,12 +207,15 @@ static unsigned long __kprobes relbranch_fixup(u32 insn, struct kprobe *p,
>  	if (regs->tnpc == regs->tpc + 0x4UL)
>  		return real_pc + 0x8UL;
>  
> -	/* The three cases are call, branch w/prediction,
> -	 * and traditional branch.
> +	/* The cases are call and the branches with a PC-relative
> +	 * displacement.
>  	 */
> -	if ((insn & 0xc0000000) == 0x40000000 ||
> -	    (insn & 0xc1c00000) == 0x00400000 ||
> -	    (insn & 0xc1c00000) == 0x00800000) {
> +	if ((insn & 0xc0000000) == 0x40000000 ||	/* call */
> +	    (insn & 0xc1c00000) == 0x00400000 ||	/* BPcc */
> +	    (insn & 0xc1c00000) == 0x00800000 ||	/* Bicc */
> +	    (insn & 0xd1c00000) == 0x00c00000 ||	/* BPr */
> +	    (insn & 0xc1c00000) == 0x01400000 ||	/* FBPfcc */
> +	    (insn & 0xc1c00000) == 0x01800000) {	/* FBfcc */
>  		unsigned long ainsn_addr;
>  
>  		ainsn_addr = (unsigned long) &p->ainsn.insn[0];
> -- 
> 2.55.0
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2026-09-25 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 14:49 [PATCH 0/2] sparc64: " Danish Khateeb
2026-09-23 14:49 ` [PATCH 1/2] sparc64: kprobes: " Danish Khateeb
2026-09-25 14:28   ` Masami Hiramatsu [this message]
2026-09-23 14:54 ` [PATCH 2/2] sparc64: uprobes: " Danish Khateeb

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=20260925232822.094082fd46fb3b02d9cfff10@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=allen.lkml@gmail.com \
    --cc=andreas@gaisler.com \
    --cc=danishkhateeb03@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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®