public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kai Zhang <zhangkai@iscas.ac.cn>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	stable@vger.kernel.org
Subject: Re: [linux-6.6.y bugreport] riscv: kprobe crash as some patchs lost
Date: Tue, 22 Apr 2025 10:46:13 +0200	[thread overview]
Message-ID: <2025042250-backlash-shifting-89cf@gregkh> (raw)
In-Reply-To: <c7e463c0-8cad-4f4e-addd-195c06b7b6de@iscas.ac.cn>

On Tue, Apr 22, 2025 at 10:58:42AM +0800, Kai Zhang wrote:
> In most recent linux-6.6.y tree,
> `arch/riscv/kernel/probes/kprobes.c::arch_prepare_ss_slot` still has the
> obsolete code:
> 
>     u32 insn = __BUG_INSN_32;
>     unsigned long offset = GET_INSN_LENGTH(p->opcode);
>     p->ainsn.api.restore = (unsigned long)p->addr + offset;
>     patch_text_nosync(p->ainsn.api.insn, &p->opcode, 1);
>     patch_text_nosync((void *)p->ainsn.api.insn + offset, &insn, 1);
> 
> The last two 1s are wrong size of written instructions , which would lead to
> kernel crash, like `insmod kprobe_example.ko` gives:
> 
> [  509.812815][ T2734] kprobe_init: Planted kprobe at 00000000c5c46130
> [  509.837606][    C5] handler_pre: <kernel_clone> p->addr =
> 0x00000000c5c46130, pc = 0xffffffff80032ee2, status = 0x200000120
> [  509.839315][    C5] Oops - illegal instruction [#1]
> 
> 
> I've tried two patchs from torvalds tree and it didn't crash again:
> 
> 51781ce8f448 riscv: Pass patch_text() the length in bytes (rebased)
> 13134cc94914 riscv: kprobes: Fix incorrect address calculation

Neither of these apply cleanly.  Please provide working backports if you
wish to see them added to the tree.

thanks,

greg k-h

  reply	other threads:[~2025-04-22  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22  2:58 [linux-6.6.y bugreport] riscv: kprobe crash as some patchs lost Kai Zhang
2025-04-22  8:46 ` Greg Kroah-Hartman [this message]
2025-04-25  8:03   ` Kai Zhang
2025-04-25  8:07     ` Greg Kroah-Hartman
2025-04-25 12:09       ` Kai Zhang
2025-04-25 12:49         ` Nam Cao
2025-04-25 12:59           ` Nam Cao
2025-04-25 15:29             ` Kai Zhang
2025-04-28  7:22               ` Nam Cao
2025-04-28 12:10                 ` Kai Zhang
2025-04-25 14:53           ` Kai Zhang

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=2025042250-backlash-shifting-89cf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=stable@vger.kernel.org \
    --cc=zhangkai@iscas.ac.cn \
    /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