From: Nam Cao <namcao@linutronix.de>
To: Zongmin Zhou <min_halo@163.com>,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu
Cc: alex@ghiti.fr, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
Zongmin Zhou <zhouzongmin@kylinos.cn>
Subject: Re: [PATCH] riscv: kprobes: Reject reserved branch encodings
Date: Tue, 01 Sep 2026 20:46:50 +0200 [thread overview]
Message-ID: <87pkywajxh.fsf@yellow.woof> (raw)
In-Reply-To: <20260901115421.109573-1-min_halo@163.com>
Zongmin Zhou <min_halo@163.com> writes:
> A probe on such an encoding, e.g. placed on
> data misdecoded as instructions, therefore keeps the instruction
> pointer on the breakpoint, and the CPU traps on it forever.
How can that happen? Isn't probe on data disallowed? And how can the
instruction pointer be on data?
How did you find this issue? If this is from some LLM, please add
Assisted-by: tag.
Nam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-09-01 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 11:54 [PATCH] riscv: kprobes: Reject reserved branch encodings Zongmin Zhou
2026-09-01 18:46 ` Nam Cao [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=87pkywajxh.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=min_halo@163.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=zhouzongmin@kylinos.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.