public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kernel: enable CONFIG_DEBUG_WX on aarch64
Date: Mon, 20 Apr 2020 08:12:08 +0100	[thread overview]
Message-ID: <06820C35-4DC7-4B09-A21E-BD212666B090@ipfire.org> (raw)
In-Reply-To: <0c5a219d-21e8-9c0d-c3f5-4c516361a8d1@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 18 Apr 2020, at 09:16, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Since this is described as 'Generate a warning if any W+X mappings are
> found at boot.', it most likely does not break anything and can be
> safely enabled.
> 
> Fixes: #12373
> 
> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.aarch64-ipfire | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config/kernel/kernel.config.aarch64-ipfire b/config/kernel/kernel.config.aarch64-ipfire
> index 32ad2df07..eb914365f 100644
> --- a/config/kernel/kernel.config.aarch64-ipfire
> +++ b/config/kernel/kernel.config.aarch64-ipfire
> @@ -6572,7 +6572,7 @@ CONFIG_IO_STRICT_DEVMEM=y
> # CONFIG_ARM64_PTDUMP_DEBUGFS is not set
> # CONFIG_PID_IN_CONTEXTIDR is not set
> # CONFIG_ARM64_RANDOMIZE_TEXT_OFFSET is not set
> -# CONFIG_DEBUG_WX is not set
> +CONFIG_DEBUG_WX=y
> CONFIG_DEBUG_ALIGN_RODATA=y
> # CONFIG_ARM64_RELOC_TEST is not set
> # CONFIG_CORESIGHT is not set
> -- 
> 2.16.4


      reply	other threads:[~2020-04-20  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18  8:16 Peter Müller
2020-04-20  7:12 ` Michael Tremer [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=06820C35-4DC7-4B09-A21E-BD212666B090@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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