All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shuai Xue" <xueshuai@linux.alibaba.com>
Cc: linux-trace-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v6 3/7] riscv: ftrace: always preserve s0 in dynamic ftrace register frame
Date: Mon, 14 Sep 2026 09:32:20 +0000	[thread overview]
Message-ID: <20260914093220.BE8701F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260914092648.51254-4-xueshuai@linux.alibaba.com>

> From: Wang Han <wanghan@linux.alibaba.com>
> 
> struct __arch_ftrace_regs declares s0 unconditionally, and both
> ftrace_regs_get_frame_pointer() and ftrace_partial_regs() read it
> unconditionally. But the SAVE_ABI_REGS / RESTORE_ABI_REGS macros in
> mcount-dyn.S only stored s0 under HAVE_FUNCTION_GRAPH_FP_TEST
> (CONFIG_FUNCTION_GRAPH_TRACER && CONFIG_FRAME_POINTER). With
> CONFIG_FRAME_POINTER=n the slot held whatever was on the stack before,
> so any callback going through ftrace_partial_regs() saw a garbage
> regs->s0. RISC-V kernels default to FRAME_POINTER=y, which is why this
> has not bitten in practice.
> 
> Save and restore s0 unconditionally in the dynamic ftrace ABI register
> frame. This fixes the latent garbage-s0 case, brings the dynamic ftrace
> path in line with the static _mcount path (mcount.S SAVE_ABI_STATE
> already saves s0 unconditionally), and matches the frame layout already
> documented in the comment above SAVE_ABI_REGS. It is also a prerequisite
> for the upcoming reliable unwinder, which reads
> ftrace_regs_get_frame_pointer(fregs) directly.
> 
> The cost is one extra REG_S/REG_L pair per traced call, negligible
> compared to the overall ftrace cost; the existing FREGS_SIZE_ON_STACK
> already reserved the slot, so no extra stack space is used.
> 
> Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>
> Assisted-by: Qoder:Qwen-3.8-MAX-Preview
> Signed-off-by: Wang Han <wanghan@linux.alibaba.com>
> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914092648.51254-1-xueshuai@linux.alibaba.com?part=3


  reply	other threads:[~2026-09-14  9:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  9:26 [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch Shuai Xue
2026-09-14  9:26 ` Shuai Xue
2026-09-14  9:26 ` [PATCH v6 1/7] riscv: stacktrace: Add frame record metadata Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:40   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 2/7] riscv: stacktrace: disable KASAN and KCOV instrumentation for stacktrace.o Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:32   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 3/7] riscv: ftrace: always preserve s0 in dynamic ftrace register frame Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:32   ` sashiko-bot [this message]
2026-09-14  9:26 ` [PATCH v6 4/7] riscv: stacktrace: introduce stack-bound tracking helpers Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:33   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 5/7] riscv: stacktrace: switch to frame-pointer based unwinder Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:39   ` sashiko-bot
2026-10-09 18:59   ` Karl Mehltretter
2026-10-09 18:59     ` Karl Mehltretter
2026-10-10  3:38     ` Shuai Xue
2026-10-10  3:38       ` Shuai Xue
2026-09-14  9:26 ` [PATCH v6 6/7] riscv: Kconfig: enable HAVE_RELIABLE_STACKTRACE and HAVE_LIVEPATCH Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:38   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 7/7] selftests/livepatch: Add RISC-V syscall wrapper prefix Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:38   ` sashiko-bot
2026-09-29  7:28 ` [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch Martin Kaiser
2026-09-29  7:28   ` Martin Kaiser
2026-10-08 11:42   ` Shuai Xue
2026-10-08 11:42     ` Shuai Xue
2026-10-12  8:44     ` Martin Kaiser
2026-10-12  8:44       ` Martin Kaiser

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=20260914093220.BE8701F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=xueshuai@linux.alibaba.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 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.