From: sashiko-bot@kernel.org
To: "Jens Remus" <jremus@linux.ibm.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v16 08/20] unwind_user: Stop when reaching an outermost frame
Date: Thu, 21 May 2026 14:47:06 +0000 [thread overview]
Message-ID: <20260521144706.A1EFB1F00A3B@smtp.kernel.org> (raw)
In-Reply-To: <20260521142546.3908498-9-jremus@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly added `outermost` field in `struct unwind_user_frame` is left uninitialized in `unwind_user_next_sframe()`, causing `unwind_user_next_common()` to read stack garbage and potentially terminate unwinding prematurely.
--
commit 88bb99c2143c88573eb3287429d12baa8f4ccda7
Author: Jens Remus <jremus@linux.ibm.com>
unwind_user: Stop when reaching an outermost frame
This commit adds an indication for an outermost frame to the unwind user
frame structure. It updates the common user unwinding code to stop when
such a frame is encountered.
[ ... ]
> diff --git a/kernel/unwind/user.c b/kernel/unwind/user.c
> index 1fb2724197332..fdb1001e37505 100644
> --- a/kernel/unwind/user.c
> +++ b/kernel/unwind/user.c
> @@ -32,6 +32,12 @@ static int unwind_user_next_common(struct unwind_user_state *state,
> {
> unsigned long cfa, fp, ra;
>
> + /* Stop unwinding when reaching an outermost frame. */
> + if (frame->outermost) {
[Severity: Medium]
Could this read uninitialized stack memory during bisection?
In unwind_user_next_sframe(), struct unwind_user_frame frame is declared
on the stack without being fully zeroed. It then calls __find_fre() which
populates only some fields, leaving the new outermost field uninitialized:
unwind_user_next_sframe()
struct unwind_user_frame frame;
__find_fre()
/* populates cfa_off, ra_off, fp_off, use_fp */
unwind_user_next_common()
if (frame->outermost) { /* reads uninitialized stack memory */
If the stack memory happens to be non-zero, this could incorrectly set
state->done = true and truncate the stack trace prematurely.
While this appears to be resolved in the subsequent commit
"unwind_user/sframe: Add support for outermost frame indication", does
introducing the read here before the initialization break bisectability?
> + state->done = true;
> + return 0;
> + }
> +
> /* Get the Canonical Frame Address (CFA) */
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260521142546.3908498-1-jremus@linux.ibm.com?part=8
next prev parent reply other threads:[~2026-05-21 14:47 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 14:25 [PATCH v16 00/20] unwind_deferred: Implement sframe handling Jens Remus
2026-05-21 14:25 ` [PATCH v16 01/20] unwind_user: Add generic and arch-specific headers to MAINTAINERS Jens Remus
2026-05-21 14:25 ` [PATCH v16 02/20] unwind_user/sframe: Add support for reading .sframe headers Jens Remus
2026-05-21 14:51 ` sashiko-bot
2026-05-22 10:11 ` Jens Remus
2026-05-27 20:09 ` Steven Rostedt
2026-05-21 14:25 ` [PATCH v16 03/20] unwind_user/sframe: Store .sframe section data in per-mm maple tree Jens Remus
2026-05-21 15:04 ` sashiko-bot
2026-05-27 20:20 ` Steven Rostedt
2026-05-21 14:25 ` [PATCH v16 04/20] x86/uaccess: Add unsafe_copy_from_user() implementation Jens Remus
2026-05-21 14:25 ` [PATCH v16 05/20] unwind_user/sframe: Add support for reading .sframe contents Jens Remus
2026-05-21 15:18 ` sashiko-bot
2026-05-22 9:26 ` Jens Remus
2026-05-27 19:49 ` Steven Rostedt
2026-05-21 14:25 ` [PATCH v16 06/20] unwind_user/sframe: Detect .sframe sections in executables Jens Remus
2026-05-21 14:25 ` [PATCH v16 07/20] unwind_user/sframe: Wire up unwind_user to sframe Jens Remus
2026-05-21 14:53 ` sashiko-bot
2026-05-22 9:55 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 08/20] unwind_user: Stop when reaching an outermost frame Jens Remus
2026-05-21 14:47 ` sashiko-bot [this message]
2026-05-22 10:12 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 09/20] unwind_user/sframe: Add support for outermost frame indication Jens Remus
2026-05-21 14:25 ` [PATCH v16 10/20] unwind_user/sframe: Remove .sframe section on detected corruption Jens Remus
2026-05-21 15:19 ` sashiko-bot
2026-05-22 10:03 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 11/20] unwind_user/sframe: Show file name in debug output Jens Remus
2026-05-21 15:05 ` sashiko-bot
2026-05-22 9:58 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 12/20] unwind_user/sframe: Add .sframe validation option Jens Remus
2026-05-21 15:02 ` sashiko-bot
2026-05-22 10:08 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 13/20] unwind_user: Enable archs that pass RA in a register Jens Remus
2026-05-21 14:25 ` [PATCH v16 14/20] unwind_user: Flexible FP/RA recovery rules Jens Remus
2026-05-21 14:25 ` [PATCH v16 15/20] unwind_user: Flexible CFA " Jens Remus
2026-05-21 14:25 ` [PATCH v16 16/20] unwind_user/sframe: Add support for SFrame V3 flexible FDEs Jens Remus
2026-05-21 15:14 ` sashiko-bot
2026-05-22 10:15 ` Jens Remus
2026-05-21 14:25 ` [PATCH v16 17/20] unwind_user/sframe: Separate reading of FRE from reading of FRE data words Jens Remus
2026-05-21 14:25 ` [PATCH v16 18/20] unwind_user/sframe: Duplicate registered .sframe section data on clone/fork Jens Remus
2026-05-21 15:37 ` sashiko-bot
2026-05-21 14:25 ` [PATCH v16 19/20] unwind_user/sframe/x86: Enable sframe unwinding on x86 Jens Remus
2026-05-21 14:25 ` [PATCH v16 20/20] unwind_user/sframe: Add prctl() interface for registering .sframe sections Jens Remus
2026-05-21 15:23 ` sashiko-bot
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=20260521144706.A1EFB1F00A3B@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jremus@linux.ibm.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.