From: Jens Remus <jremus@linux.ibm.com>
To: Steven Rostedt <rostedt@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrii Nakryiko <andrii@kernel.org>,
Indu Bhagat <indu.bhagat@oracle.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Beau Belgrave <beaub@linux.microsoft.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>, Florian Weimer <fweimer@redhat.com>,
Sam James <sam@gentoo.org>
Subject: Re: [PATCH v15 01/10] unwind_user: Add user space unwinding API with frame pointer support
Date: Mon, 28 Jul 2025 17:24:52 +0200 [thread overview]
Message-ID: <5fb8ada0-d90c-4a58-a38d-97b3d0787554@linux.ibm.com> (raw)
In-Reply-To: <20250725185739.233988371@kernel.org>
On 25.07.2025 20:55, Steven Rostedt wrote:
> From: Josh Poimboeuf <jpoimboe@kernel.org>
>
> Introduce a generic API for unwinding user stacks.
>
> In order to expand user space unwinding to be able to handle more complex
> scenarios, such as deferred unwinding and reading user space information,
> create a generic interface that all architectures can use that support the
> various unwinding methods.
>
> This is an alternative method for handling user space stack traces from
> the simple stack_trace_save_user() API. This does not replace that
> interface, but this interface will be used to expand the functionality of
> user space stack walking.
>
> None of the structures introduced will be exposed to user space tooling.
>
> Support for frame pointer unwinding is added. For an architecture to
> support frame pointer unwinding it needs to enable
> CONFIG_HAVE_UNWIND_USER_FP and define ARCH_INIT_USER_FP_FRAME.
>
> By encoding the frame offsets in struct unwind_user_frame, much of this
> code can also be reused for future unwinder implementations like sframe.
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
> Co-developed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Link: https://lore.kernel.org/all/20250710164301.3094-2-mathieu.desnoyers@efficios.com/
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Co-developed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Reviewed-by: Jens Remus <jremus@linux.ibm.com>
> diff --git a/kernel/unwind/user.c b/kernel/unwind/user.c
> +static int unwind_user_next_fp(struct unwind_user_state *state)
> +{
> + struct unwind_user_frame *frame = &fp_frame;
Optional: Pointer to const?
> + unsigned long cfa, fp, ra = 0;
Nit: Is initialization of ra really required? I don't see where ra
would be getting used without being set beforehand.
> + unsigned int shift;
> +
> + if (frame->use_fp) {
> + if (state->fp < state->sp)
> + return -EINVAL;
> + cfa = state->fp;
> + } else {
> + cfa = state->sp;
> + }
> +
> + /* Get the Canonical Frame Address (CFA) */
> + cfa += frame->cfa_off;
> +
> + /* stack going in wrong direction? */
> + if (cfa <= state->sp)
> + return -EINVAL;
> +
> + /* Make sure that the address is word aligned */
> + shift = sizeof(long) == 4 ? 2 : 3;
> + if (cfa & ((1 << shift) - 1))
> + return -EINVAL;
> +
> + /* Find the Return Address (RA) */
> + if (get_user(ra, (unsigned long *)(cfa + frame->ra_off)))
> + return -EINVAL;
> +
> + if (frame->fp_off && get_user(fp, (unsigned long __user *)(cfa + frame->fp_off)))
> + return -EINVAL;
> +
> + state->ip = ra;
> + state->sp = cfa;
> + if (frame->fp_off)
> + state->fp = fp;
> + return 0;
> +}
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303)
+49-7031-16-1128 Office
jremus@de.ibm.com
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
next prev parent reply other threads:[~2025-07-28 15:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 18:55 [PATCH v15 00/10] unwind_user: Deferred unwinding infrastructure Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 01/10] unwind_user: Add user space unwinding API with frame pointer support Steven Rostedt
2025-07-28 15:24 ` Jens Remus [this message]
2025-07-28 16:08 ` Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 02/10] unwind_user/deferred: Add unwind_user_faultable() Steven Rostedt
2025-07-28 15:29 ` Jens Remus
2025-07-25 18:55 ` [PATCH v15 03/10] unwind_user/deferred: Add unwind cache Steven Rostedt
2025-07-28 15:46 ` Jens Remus
2025-07-28 16:15 ` Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 04/10] unwind_user/deferred: Add deferred unwinding interface Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 05/10] unwind_user/deferred: Make unwind deferral requests NMI-safe Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 06/10] unwind deferred: Use bitmask to determine which callbacks to call Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 07/10] unwind deferred: Add unwind_completed mask to stop spurious callbacks Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 08/10] unwind: Add USED bit to only have one conditional on way back to user space Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 09/10] unwind deferred: Use SRCU unwind_deferred_task_work() Steven Rostedt
2025-07-25 18:55 ` [PATCH v15 10/10] unwind: Finish up unwind when a task exits Steven Rostedt
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=5fb8ada0-d90c-4a58-a38d-97b3d0787554@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=axboe@kernel.dk \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=fweimer@redhat.com \
--cc=indu.bhagat@oracle.com \
--cc=jemarch@gnu.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@kernel.org \
--cc=sam@gentoo.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).