From: Steven Rostedt <rostedt@kernel.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
bpf@vger.kernel.org, sashiko@lists.linux.dev,
Indu Bhagat <ibhagatgnu@gmail.com>
Subject: Re: [PATCH v14 08/19] unwind_user: Stop when reaching an outermost frame
Date: Wed, 6 May 2026 11:40:50 -0400 [thread overview]
Message-ID: <20260506114050.5497b61e@fedora> (raw)
In-Reply-To: <05f795f1-0c04-4b49-9051-beb6c146991f@linux.ibm.com>
On Wed, 6 May 2026 17:01:17 +0200
Jens Remus <jremus@linux.ibm.com> wrote:
> > I note that this is fixed later in the series by the commit
> > "unwind_user/sframe: Add support for outermost frame indication", but
> > introducing the uninitialized read in this commit could break kernel
> > bisectability.
>
> Or should I merge this and the following commit into one? Or disregard?
Sframe isn't even able to be enabled yet in the series here, thus
bisection should not be a problem. The only issues with bisections we
need to worry about before sframes are enabled, is compiler errors.
That is, every patch should be able to be built.
In other words, you can safely disregard it.
-- Steve
prev parent reply other threads:[~2026-05-06 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260505121718.3572346-9-jremus@linux.ibm.com>
[not found] ` <20260505124034.B339EC2BCB4@smtp.kernel.org>
2026-05-06 15:01 ` [PATCH v14 08/19] unwind_user: Stop when reaching an outermost frame Jens Remus
2026-05-06 15:40 ` Steven Rostedt [this message]
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=20260506114050.5497b61e@fedora \
--to=rostedt@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ibhagatgnu@gmail.com \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox