From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro
Date: Tue, 29 May 2018 10:21:34 +0100 [thread overview]
Message-ID: <20180529092133.GA6533@arm.com> (raw)
In-Reply-To: <20180528033353.54725-1-nixiaoming@huawei.com>
On Mon, May 28, 2018 at 11:33:53AM +0800, nixiaoming wrote:
> Signed-off-by: nixiaoming <nixiaoming@huawei.com>
Please can you write a commit message explaining what this fixes and also
give me a pointer to patches 2 and 3 from this series?
Will
> ---
> arch/arm64/mm/mmu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> index 2dbb2c9..849f326 100644
> --- a/arch/arm64/mm/mmu.c
> +++ b/arch/arm64/mm/mmu.c
> @@ -491,6 +491,7 @@ static void __init map_mem(pgd_t *pgdp)
> #endif
> }
>
> +#ifdef CONFIG_STRICT_KERNEL_RWX
> void mark_rodata_ro(void)
> {
> unsigned long section_size;
> @@ -505,6 +506,7 @@ void mark_rodata_ro(void)
>
> debug_checkwx();
> }
> +#endif
>
> static void __init map_kernel_segment(pgd_t *pgdp, void *va_start, void *va_end,
> pgprot_t prot, struct vm_struct *vma,
> --
> 2.10.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: nixiaoming <nixiaoming@huawei.com>
Cc: catalin.marinas@arm.com, ard.biesheuvel@linaro.org,
marc.zyngier@arm.com, james.morse@arm.com,
kristina.martsenko@arm.com, steve.capper@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro
Date: Tue, 29 May 2018 10:21:34 +0100 [thread overview]
Message-ID: <20180529092133.GA6533@arm.com> (raw)
In-Reply-To: <20180528033353.54725-1-nixiaoming@huawei.com>
On Mon, May 28, 2018 at 11:33:53AM +0800, nixiaoming wrote:
> Signed-off-by: nixiaoming <nixiaoming@huawei.com>
Please can you write a commit message explaining what this fixes and also
give me a pointer to patches 2 and 3 from this series?
Will
> ---
> arch/arm64/mm/mmu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c
> index 2dbb2c9..849f326 100644
> --- a/arch/arm64/mm/mmu.c
> +++ b/arch/arm64/mm/mmu.c
> @@ -491,6 +491,7 @@ static void __init map_mem(pgd_t *pgdp)
> #endif
> }
>
> +#ifdef CONFIG_STRICT_KERNEL_RWX
> void mark_rodata_ro(void)
> {
> unsigned long section_size;
> @@ -505,6 +506,7 @@ void mark_rodata_ro(void)
>
> debug_checkwx();
> }
> +#endif
>
> static void __init map_kernel_segment(pgd_t *pgdp, void *va_start, void *va_end,
> pgprot_t prot, struct vm_struct *vma,
> --
> 2.10.1
>
next prev parent reply other threads:[~2018-05-29 9:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 3:33 [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro nixiaoming
2018-05-28 3:33 ` nixiaoming
2018-05-29 9:21 ` Will Deacon [this message]
2018-05-29 9:21 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2018-05-29 13:36 nixiaoming
2018-05-29 13:36 ` nixiaoming
2018-05-29 15:45 ` Will Deacon
2018-05-29 15:45 ` Will Deacon
2018-05-30 3:31 ` Nixiaoming
2018-05-30 3:31 ` Nixiaoming
2018-05-30 8:08 ` Mark Rutland
2018-05-30 8:08 ` Mark Rutland
2018-05-30 9:05 ` Nixiaoming
2018-05-30 9:05 ` Nixiaoming
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=20180529092133.GA6533@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.