From: Laura Abbott <labbott@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>, Russell King <linux@armlinux.org.uk>
Cc: Kees Cook <keescook@chromium.org>,
Jinbum Park <jinb.park7@gmail.com>,
Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: make CONFIG_DEBUG_WX depend on MMU
Date: Tue, 20 Feb 2018 08:45:10 -0800 [thread overview]
Message-ID: <bea07eb7-1763-147c-9da5-e70d2fcf876b@redhat.com> (raw)
In-Reply-To: <20180220150932.3285766-1-arnd@arndb.de>
On 02/20/2018 07:09 AM, Arnd Bergmann wrote:
> Without CONFIG_MMU, this results in a build failure:
>
> ./arch/arm/include/asm/memory.h:92:23: error: initializer element is not constant
> #define VECTORS_BASE vectors_base
> arch/arm/mm/dump.c:32:4: note: in expansion of macro 'VECTORS_BASE'
> { VECTORS_BASE, "Vectors" },
>
> arch/arm/mm/dump.c:71:11: error: 'L_PTE_USER' undeclared here (not in a function); did you mean 'VTIME_USER'?
> .mask = L_PTE_USER,
> ^~~~~~~~~~
>
> Obviously the feature only makes sense with an MMU, so let's add the
> dependency here.
>
Acked-by: Laura Abbott <labbott@redhat.com>
> Fixes: a8e53c151fe7 ("ARM: 8737/1: mm: dump: add checking for writable and executable")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> arch/arm/Kconfig.debug | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index 7b3d9c5c73bb..6db106b5b9e9 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -22,6 +22,7 @@ config ARM_PTDUMP_DEBUGFS
>
> config DEBUG_WX
> bool "Warn on W+X mappings at boot"
> + depends on MMU
> select ARM_PTDUMP_CORE
> ---help---
> Generate a warning if any W+X mappings are found at boot.
>
prev parent reply other threads:[~2018-02-20 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 15:09 Arnd Bergmann
2018-02-20 16:45 ` Laura Abbott [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=bea07eb7-1763-147c-9da5-e70d2fcf876b@redhat.com \
--to=labbott@redhat.com \
--cc=arnd@arndb.de \
--cc=jinb.park7@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tony@atomide.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
Powered by JetHome