From: Martin Kaiser <martin@kaiser.cx>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: palmer@dabbelt.com, pjw@kernel.org, aou@eecs.berkeley.edu,
alex@ghiti.fr, linux-riscv@lists.infradead.org, oleg@redhat.com,
rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, jpoimboe@kernel.org, jikos@kernel.org,
mbenes@suse.cz, pmladek@suse.com, joe.lawrence@redhat.com,
shuah@kernel.org, mpdesouza@suse.com,
oliver.yang@linux.alibaba.com, zhuo.song@linux.alibaba.com,
jkchen@linux.alibaba.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, live-patching@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch
Date: Tue, 29 Sep 2026 09:28:13 +0200 [thread overview]
Message-ID: <artojcJftbMIgPrj@akranes.kaiser.cx> (raw)
In-Reply-To: <20260914092648.51254-1-xueshuai@linux.alibaba.com>
Thus wrote Shuai Xue (xueshuai@linux.alibaba.com):
> Hi,
> This is v6 of the RISC-V reliable stack unwinding series for livepatch.
> Wang Han has left our team, so I am taking over this series from now on.
> The series adds explicit frame-record metadata, preserves the frame
> pointer through dynamic ftrace, and replaces the open-coded stack walker
> with a conservative frame-pointer based unwinder. It then enables the
> RISC-V livepatch capability and adds the syscall-wrapper selftest prefix.
> Changes since v5:
> * Rebase onto the current riscv/for-next; no functional changes.
> * Fold in the tags collected from the v5 thread:
> - Reviewed-by: Shuai Xue on 2/7, 3/7, 4/7 and 6/7
> - Acked-by: Miroslav Benes on 7/7
> * Add my sign-off as the new sender.
> Since the patches are otherwise identical to v5, the v5 validation
> results still apply. For reference, from the v5 cover letter:
> * Built Linux 7.2.0-rc6 with riscv64-unknown-linux-gnu-gcc 15.2.0
> and binutils 2.46.
> * Standard livepatch configuration built successfully, including
> Image, vmlinux, modules, compile_commands.json and GDB scripts.
> * CONFIG_IRQ_STACKS=n variant linked successfully with GCC.
> * QEMU 8.2.2, 1 CPU: livepatch selftests PASS: 7, SKIP: 1,
> FAIL: 0; ftrace function graph 3 passed, 0 failed, 3 unsupported.
> * QEMU 8.2.2, 4 CPUs: livepatch selftests PASS: 7, SKIP: 1,
> FAIL: 0; ftrace function graph 3 passed, 0 failed, 3 unsupported.
> * No BUG, WARNING, Oops, panic, unreliable stack or Call Trace found
> by the validation log scans. Expected negative livepatch errors are
> part of the selftests.
> v5 was posted in early August and has been quiet since then. I would
> appreciate it if the series could be considered for the upcoming merge
> window. Happy to address any remaining feedback.
> Base:
> riscv/for-next 77ae27fd98f3 ("Merge tag 'printk-for-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux")
> Previous versions:
> v5: https://lore.kernel.org/r/20260804103626.2803112-1-wanghan@linux.alibaba.com
> v4 RESEND: https://lore.kernel.org/r/20260629072713.3273743-1-wanghan@linux.alibaba.com
> v3: https://lore.kernel.org/r/cover.194d76e3a15b.v3.riscv-livepatch.wanghan@linux.alibaba.com
> v2: https://lore.kernel.org/r/20260528082310.1994388-1-wanghan@linux.alibaba.com
> v1: https://lore.kernel.org/r/20260527123530.2593918-1-wanghan@linux.alibaba.com
> Assisted-by: Qoder:Qwen-3.8-MAX-Preview
Thanks for these patches.
I tried them on a standard rv64 qemu and on a rv64 cheri system
(cheri-linux.org). The latter needed some minor tweaks, but in
both cases, I could get livepatch to work.
Reviewed-by: Martin Kaiser <martin@kaiser.cx>
Tested-by: Martin Kaiser <martin@kaiser.cx>
WARNING: multiple messages have this Message-ID (diff)
From: Martin Kaiser <martin@kaiser.cx>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: palmer@dabbelt.com, pjw@kernel.org, aou@eecs.berkeley.edu,
alex@ghiti.fr, linux-riscv@lists.infradead.org, oleg@redhat.com,
rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, jpoimboe@kernel.org, jikos@kernel.org,
mbenes@suse.cz, pmladek@suse.com, joe.lawrence@redhat.com,
shuah@kernel.org, mpdesouza@suse.com,
oliver.yang@linux.alibaba.com, zhuo.song@linux.alibaba.com,
jkchen@linux.alibaba.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, live-patching@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch
Date: Tue, 29 Sep 2026 09:28:13 +0200 [thread overview]
Message-ID: <artojcJftbMIgPrj@akranes.kaiser.cx> (raw)
In-Reply-To: <20260914092648.51254-1-xueshuai@linux.alibaba.com>
Thus wrote Shuai Xue (xueshuai@linux.alibaba.com):
> Hi,
> This is v6 of the RISC-V reliable stack unwinding series for livepatch.
> Wang Han has left our team, so I am taking over this series from now on.
> The series adds explicit frame-record metadata, preserves the frame
> pointer through dynamic ftrace, and replaces the open-coded stack walker
> with a conservative frame-pointer based unwinder. It then enables the
> RISC-V livepatch capability and adds the syscall-wrapper selftest prefix.
> Changes since v5:
> * Rebase onto the current riscv/for-next; no functional changes.
> * Fold in the tags collected from the v5 thread:
> - Reviewed-by: Shuai Xue on 2/7, 3/7, 4/7 and 6/7
> - Acked-by: Miroslav Benes on 7/7
> * Add my sign-off as the new sender.
> Since the patches are otherwise identical to v5, the v5 validation
> results still apply. For reference, from the v5 cover letter:
> * Built Linux 7.2.0-rc6 with riscv64-unknown-linux-gnu-gcc 15.2.0
> and binutils 2.46.
> * Standard livepatch configuration built successfully, including
> Image, vmlinux, modules, compile_commands.json and GDB scripts.
> * CONFIG_IRQ_STACKS=n variant linked successfully with GCC.
> * QEMU 8.2.2, 1 CPU: livepatch selftests PASS: 7, SKIP: 1,
> FAIL: 0; ftrace function graph 3 passed, 0 failed, 3 unsupported.
> * QEMU 8.2.2, 4 CPUs: livepatch selftests PASS: 7, SKIP: 1,
> FAIL: 0; ftrace function graph 3 passed, 0 failed, 3 unsupported.
> * No BUG, WARNING, Oops, panic, unreliable stack or Call Trace found
> by the validation log scans. Expected negative livepatch errors are
> part of the selftests.
> v5 was posted in early August and has been quiet since then. I would
> appreciate it if the series could be considered for the upcoming merge
> window. Happy to address any remaining feedback.
> Base:
> riscv/for-next 77ae27fd98f3 ("Merge tag 'printk-for-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux")
> Previous versions:
> v5: https://lore.kernel.org/r/20260804103626.2803112-1-wanghan@linux.alibaba.com
> v4 RESEND: https://lore.kernel.org/r/20260629072713.3273743-1-wanghan@linux.alibaba.com
> v3: https://lore.kernel.org/r/cover.194d76e3a15b.v3.riscv-livepatch.wanghan@linux.alibaba.com
> v2: https://lore.kernel.org/r/20260528082310.1994388-1-wanghan@linux.alibaba.com
> v1: https://lore.kernel.org/r/20260527123530.2593918-1-wanghan@linux.alibaba.com
> Assisted-by: Qoder:Qwen-3.8-MAX-Preview
Thanks for these patches.
I tried them on a standard rv64 qemu and on a rv64 cheri system
(cheri-linux.org). The latter needed some minor tweaks, but in
both cases, I could get livepatch to work.
Reviewed-by: Martin Kaiser <martin@kaiser.cx>
Tested-by: Martin Kaiser <martin@kaiser.cx>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-09-29 8:13 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
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 ` Martin Kaiser [this message]
2026-09-29 7:28 ` [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch 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=artojcJftbMIgPrj@akranes.kaiser.cx \
--to=martin@kaiser.cx \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jikos@kernel.org \
--cc=jkchen@linux.alibaba.com \
--cc=joe.lawrence@redhat.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mbenes@suse.cz \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpdesouza@suse.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=oliver.yang@linux.alibaba.com \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=xueshuai@linux.alibaba.com \
--cc=zhuo.song@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.