linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: page-align sections for DEBUG_RODATA
Date: Tue, 27 Oct 2015 10:56:33 +0000	[thread overview]
Message-ID: <20151027105632.GA3091@leverpostej> (raw)
In-Reply-To: <CAKv+Gu-jCxeQt1DffTnYiMLT-jB75GiQCOUR7GqNH7hAeB84LA@mail.gmail.com>

On Tue, Oct 27, 2015 at 11:37:04AM +0900, Ard Biesheuvel wrote:
> On 27 October 2015 at 06:42, Mark Rutland <mark.rutland@arm.com> wrote:
> > A kernel built with DEBUG_RO_DATA && !CONFIG_DEBUG_ALIGN_RODATA doesn't
> > have .text aligned to a page boundary, though fixup_executable works at
> > page-granularity thanks to its use of create_mapping. If .text is not
> > page-aligned, the first page it exists in may be marked non-executable,
> > leading to failures when an attempt is made to execute code in said
> > page.
> >
> > This patch upgrades ALIGN_DEBUG_RO and ALIGN_DEBUG_RO_MIN to force page
> > alignment for DEBUG_RO_DATA && !CONFIG_DEBUG_ALIGN_RODATA kernels,
> > ensuring that all sections with specific RWX permission requirements are
> > mapped with the correct permissions.
> >
> > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > Reported-by: Jeremy Linton <jeremy.linton@arm.com>
> > Reviewed-by: Laura Abbott <laura@labbott.name>
> > Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > Cc: Suzuki Poulose <suzuki.poulose@arm.com>
> > Cc: Will Deacon <will.deacon@arm.com>
> > ---
> >  arch/arm64/kernel/vmlinux.lds.S | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > Note: this is intended to supercede [1,2].
> >
> > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/380486.html
> > [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/380999.html
> >
> > diff --git a/arch/arm64/kernel/vmlinux.lds.S b/arch/arm64/kernel/vmlinux.lds.S
> > index 9807333..4d77757 100644
> > --- a/arch/arm64/kernel/vmlinux.lds.S
> > +++ b/arch/arm64/kernel/vmlinux.lds.S
> > @@ -60,9 +60,12 @@ PECOFF_FILE_ALIGNMENT = 0x200;
> >  #define PECOFF_EDATA_PADDING
> >  #endif
> >
> > -#ifdef CONFIG_DEBUG_ALIGN_RODATA
> > +#if defined(CONFIG_DEBUG_ALIGN_RODATA)
> >  #define ALIGN_DEBUG_RO                 . = ALIGN(1<<SECTION_SHIFT);
> >  #define ALIGN_DEBUG_RO_MIN(min)                ALIGN_DEBUG_RO
> > +#elif defined(CONFIG_DEBUG_RODATA)
> > +#define ALIGN_DEBUG_RO                 . = ALIGN(1<<PAGE_SHIFT);
> > +#define ALIGN_DEBUG_RO_MIN(min)                ALIGN_DEBUG_RO
> >  #else
> >  #define ALIGN_DEBUG_RO
> >  #define ALIGN_DEBUG_RO_MIN(min)                . = ALIGN(min);
> 
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

Cheers, Ard.

Jeremy, does this work for you?

If so, I expect Catalin will take this for 4.4, with the addition of any
Acks and:

Fixes: da141706aea52c1a ("arm64: add better page protections to arm64")
Cc: <stable@vger.kernel.org>

Thanks,
Mark.

  reply	other threads:[~2015-10-27 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 21:42 [PATCH] arm64: page-align sections for DEBUG_RODATA Mark Rutland
2015-10-27  2:37 ` Ard Biesheuvel
2015-10-27 10:56   ` Mark Rutland [this message]
2015-10-29 17:25     ` 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=20151027105632.GA3091@leverpostej \
    --to=mark.rutland@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 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).