From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jungseung Lee <js07.lee@samsung.com>
Cc: linus.walleij@linaro.org, amit.kachhap@arm.com, ardb@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, keescook@chromium.org,
js07.lee@gmail.com
Subject: Re: [PATCH 1/2] arm/mm : omit [_text, _stext) from kernel code region
Date: Mon, 6 Mar 2023 11:06:05 +0000 [thread overview]
Message-ID: <ZAXJHbHAhD42o36F@shell.armlinux.org.uk> (raw)
In-Reply-To: <1678081915-12599-1-git-send-email-js07.lee@samsung.com>
On Mon, Mar 06, 2023 at 02:51:54PM +0900, Jungseung Lee wrote:
> The resource reservations in /proc/iomem made for the kernel code did
> not reflect the gaps between pagetable and text.
>
> In particular, if the CONFIG_STRICT_KERNEL_RWX option is turned on,
> the wrong area is shown as the kernel code area.
>
> Fix it by removing [_text, _stext) from kernel code region.
>
> Before:
> 04000000-2f7fffff : System RAM
> 04008000-04cfffff : Kernel code
> 04e00000-05369a27 : Kernel data
>
> After :
> 04000000-2f7fffff : System RAM
> 04100000-04cfffff : Kernel code
> 04e00000-05369a27 : Kernel data
And why do you think this is correct? Isn't the head text, which
isn't discarded and is located at 0x04008000, still part of kernel
code?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-06 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230306061055epcas1p1f7718c46c10f84845e086f9ce9f9a41f@epcas1p1.samsung.com>
2023-03-06 5:51 ` [PATCH 1/2] arm/mm : omit [_text, _stext) from kernel code region Jungseung Lee
2023-03-06 5:51 ` [PATCH 2/2] arm/mm : Report actual image regions in /proc/iomem Jungseung Lee
2023-03-06 11:10 ` Russell King (Oracle)
2023-03-06 12:14 ` Jungseung Lee
2023-03-06 12:28 ` Russell King (Oracle)
2023-03-06 13:00 ` Ard Biesheuvel
2023-03-06 11:06 ` Russell King (Oracle) [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=ZAXJHbHAhD42o36F@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=amit.kachhap@arm.com \
--cc=ardb@kernel.org \
--cc=js07.lee@gmail.com \
--cc=js07.lee@samsung.com \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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).