From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: broonie@kernel.org, catalin.marinas@arm.com, mbenes@suse.cz,
puranjay12@gmail.com, will@kernel.org
Subject: Re: [PATCH] arm64: preserve pt_regs::stackframe during exec*()
Date: Mon, 21 Oct 2024 18:13:07 +0100 [thread overview]
Message-ID: <ZxaLlUDf8vqNlXPt@J2N7QTR9R3> (raw)
In-Reply-To: <20241021164456.2275285-1-mark.rutland@arm.com>
On Mon, Oct 21, 2024 at 05:44:56PM +0100, Mark Rutland wrote:
> When performing an exec*(), there's a transient period before the return
> to userspace where any stacktrace will result in a warning triggered by
> kunwind_next_frame_record_meta() encountering a struct frame_record_meta
> with an unknown type. This can be seen fairly reliably by enabling KASAN
> or KFENCE, e.g.
[...]
> This zeroing wasn't a problem prior to commit:
>
> 0f0b9a3f6a50fa36 ("arm64: stacktrace: unwind exception boundaries")
Sorry, that's the commit ID from my arm64/stacktrace/metadata branch.
The version queued in the arm64 for-next/stacktrace branch has a
different ID, and this should say:
c2c6b27b5aa14fa2 ("arm64: stacktrace: unwind exception boundaries")
[...]
> Fixes: 0f0b9a3f6a50fa36 ("arm64: stacktrace: unwind exception boundaries")
... and likewise that should be:
Fixes: c2c6b27b5aa14fa2 ("arm64: stacktrace: unwind exception boundaries")
Mark.
next prev parent reply other threads:[~2024-10-21 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 16:44 [PATCH] arm64: preserve pt_regs::stackframe during exec*() Mark Rutland
2024-10-21 17:13 ` Mark Rutland [this message]
2024-10-21 19:40 ` Puranjay Mohan
2024-10-22 11:37 ` Catalin Marinas
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=ZxaLlUDf8vqNlXPt@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mbenes@suse.cz \
--cc=puranjay12@gmail.com \
--cc=will@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