Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rui Qi" <qirui.001@bytedance.com>
To: <rostedt@goodmis.org>, <mhiramat@kernel.org>
Cc: "Rui Qi" <qirui.001@bytedance.com>, <mark.rutland@arm.com>,
	 <pjw@kernel.org>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
	 <alex@ghiti.fr>, <linux-kernel@vger.kernel.org>,
	 <linux-trace-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH] riscv: ftrace: reject out-of-range non-direct targets
Date: Mon, 31 Aug 2026 11:50:45 +0800	[thread overview]
Message-ID: <20260901020000.1-qirui.001@bytedance.com> (raw)
In-Reply-To: <20260707121235.759104-1-qirui.001@bytedance.com>

Hi Steven,

Gentle ping on this patch. It's been over a month since submission
and I'd appreciate your review when you have a chance.

The patch fixes ftrace_modify_call() on RISC-V to properly validate
old_addr/addr instead of always treating sites as FTRACE_ADDR, and
rejects out-of-range non-direct targets that can't be dispatched
through the existing ftrace_caller path.

Thanks,
Rui

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-08-31  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 12:12 [PATCH] riscv: ftrace: reject out-of-range non-direct targets Rui Qi
2026-08-31  3:50 ` Rui Qi [this message]
2026-08-31 14:58   ` Steven Rostedt
2026-09-01  2:29     ` Rui Qi

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=20260901020000.1-qirui.001@bytedance.com \
    --to=qirui.001@bytedance.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=rostedt@goodmis.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