From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Omar Sandoval <osandov@osandov.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-debuggers@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2] arm64: map [_text, _stext) virtual address range non-executable+read-only
Date: Mon, 22 Sep 2025 14:14:48 +0100 [thread overview]
Message-ID: <175853869848.3126168.11981509234580321695.b4-ty@kernel.org> (raw)
In-Reply-To: <93a6f8e47cce118493e250b719a927f517be12cf.1758316750.git.osandov@osandov.com>
On Fri, 19 Sep 2025 14:27:51 -0700, Omar Sandoval wrote:
> Since the referenced fixes commit, the kernel's .text section is only
> mapped starting from _stext; the region [_text, _stext) is omitted. As a
> result, other vmalloc/vmap allocations may use the virtual addresses
> nominally in the range [_text, _stext). This address reuse confuses
> multiple things:
>
> 1. crash_prepare_elf64_headers() sets up a segment in /proc/vmcore
> mapping the entire range [_text, _end) to
> [__pa_symbol(_text), __pa_symbol(_end)). Reading an address in
> [_text, _stext) from /proc/vmcore therefore gives the incorrect
> result.
> 2. Tools doing symbolization (either by reading /proc/kallsyms or based
> on the vmlinux ELF file) will incorrectly identify vmalloc/vmap
> allocations in [_text, _stext) as kernel symbols.
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: map [_text, _stext) virtual address range non-executable+read-only
https://git.kernel.org/arm64/c/5973a62efa34
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-09-22 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 21:27 [PATCH v2] arm64: map [_text, _stext) virtual address range non-executable+read-only Omar Sandoval
2025-09-22 13:14 ` Will Deacon [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=175853869848.3126168.11981509234580321695.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kernel-team@fb.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=osandov@osandov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox