From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Kees Cook <keescook@chromium.org>,
Russell Currey <ruscur@russell.cc>,
"jniethe5@gmail.com" <jniethe5@gmail.com>
Cc: "ajd@linux.ibm.com" <ajd@linux.ibm.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"dja@axtens.net" <dja@axtens.net>
Subject: Re: [PATCH v5 3/8] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime
Date: Thu, 7 Apr 2022 07:39:51 +0000 [thread overview]
Message-ID: <237d8319-8127-c0fe-a855-ca04408bc925@csgroup.eu> (raw)
In-Reply-To: <202204061154.5A685C10D@keescook>
Le 06/04/2022 à 20:55, Kees Cook a écrit :
> *thread necromancy*
>
> Is this patch still something folks are working on? It'd be nice to be
> able to trigger this check at runtime.
The series was taken over by Jordan.
v15 of the series was accepted, but that particular patch was dropped in
v11 (see
https://patchwork.ozlabs.org/project/linuxppc-dev/cover/20210429031602.2606654-1-jniethe5@gmail.com/)
The comment was:
Some patches were dropped from this revision:
powerpc/mm/ptdump: debugfs handler for W+X checks at runtime
- Will use Christophe's generic ptdump series
Not sure what happened after that.
Christophe
>
> -Kees
>
> On Wed, Feb 26, 2020 at 05:35:46PM +1100, Russell Currey wrote:
>> Very rudimentary, just
>>
>> echo 1 > [debugfs]/check_wx_pages
>>
>> and check the kernel log. Useful for testing strict module RWX.
>>
>> Updated the Kconfig entry to reflect this.
>>
>> Also fixed a typo.
>>
>> Signed-off-by: Russell Currey <ruscur@russell.cc>
>> ---
>> arch/powerpc/Kconfig.debug | 6 ++++--
>> arch/powerpc/mm/ptdump/ptdump.c | 21 ++++++++++++++++++++-
>> 2 files changed, 24 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug
>> index 0b063830eea8..e37960ef68c6 100644
>> --- a/arch/powerpc/Kconfig.debug
>> +++ b/arch/powerpc/Kconfig.debug
>> @@ -370,7 +370,7 @@ config PPC_PTDUMP
>> If you are unsure, say N.
>>
>> config PPC_DEBUG_WX
>> - bool "Warn on W+X mappings at boot"
>> + bool "Warn on W+X mappings at boot & enable manual checks at runtime"
>> depends on PPC_PTDUMP && STRICT_KERNEL_RWX
>> help
>> Generate a warning if any W+X mappings are found at boot.
>> @@ -384,7 +384,9 @@ config PPC_DEBUG_WX
>> of other unfixed kernel bugs easier.
>>
>> There is no runtime or memory usage effect of this option
>> - once the kernel has booted up - it's a one time check.
>> + once the kernel has booted up, it only automatically checks once.
>> +
>> + Enables the "check_wx_pages" debugfs entry for checking at runtime.
>>
>> If in doubt, say "Y".
>>
>> diff --git a/arch/powerpc/mm/ptdump/ptdump.c b/arch/powerpc/mm/ptdump/ptdump.c
>> index 206156255247..a15e19a3b14e 100644
>> --- a/arch/powerpc/mm/ptdump/ptdump.c
>> +++ b/arch/powerpc/mm/ptdump/ptdump.c
>> @@ -4,7 +4,7 @@
>> *
>> * This traverses the kernel pagetables and dumps the
>> * information about the used sections of memory to
>> - * /sys/kernel/debug/kernel_pagetables.
>> + * /sys/kernel/debug/kernel_page_tables.
>> *
>> * Derived from the arm64 implementation:
>> * Copyright (c) 2014, The Linux Foundation, Laura Abbott.
>> @@ -413,6 +413,25 @@ void ptdump_check_wx(void)
>> else
>> pr_info("Checked W+X mappings: passed, no W+X pages found\n");
>> }
>> +
>> +static int check_wx_debugfs_set(void *data, u64 val)
>> +{
>> + if (val != 1ULL)
>> + return -EINVAL;
>> +
>> + ptdump_check_wx();
>> +
>> + return 0;
>> +}
>> +
>> +DEFINE_SIMPLE_ATTRIBUTE(check_wx_fops, NULL, check_wx_debugfs_set, "%llu\n");
>> +
>> +static int ptdump_check_wx_init(void)
>> +{
>> + return debugfs_create_file("check_wx_pages", 0200, NULL,
>> + NULL, &check_wx_fops) ? 0 : -ENOMEM;
>> +}
>> +device_initcall(ptdump_check_wx_init);
>> #endif
>>
>> static int ptdump_init(void)
>> --
>> 2.25.1
>>
>
next prev parent reply other threads:[~2022-04-07 7:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 6:35 [PATCH v5 0/8] set_memory() routines and STRICT_MODULE_RWX Russell Currey
2020-02-26 6:35 ` [PATCH v5 1/8] powerpc/mm: Implement set_memory() routines Russell Currey
2020-02-26 6:35 ` [PATCH v5 2/8] powerpc/kprobes: Mark newly allocated probes as RO Russell Currey
2020-02-26 6:35 ` [PATCH v5 3/8] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime Russell Currey
2020-02-26 21:52 ` Kees Cook
2022-04-06 18:55 ` Kees Cook
2022-04-07 7:39 ` Christophe Leroy [this message]
2020-02-26 6:35 ` [PATCH v5 4/8] powerpc: Set ARCH_HAS_STRICT_MODULE_RWX Russell Currey
2020-02-26 6:35 ` [PATCH v5 5/8] powerpc/configs: Enable STRICT_MODULE_RWX in skiroot_defconfig Russell Currey
2020-02-26 6:35 ` [PATCH v5 6/8] powerpc/mm: implement set_memory_attr() Russell Currey
2020-02-26 6:35 ` [PATCH v5 7/8] powerpc/32: use set_memory_attr() Russell Currey
2020-02-26 6:35 ` [PATCH v5 8/8] powerpc/mm: Disable set_memory() routines when strict RWX isn't enabled Russell Currey
2020-02-26 6:38 ` Andrew Donnellan
2020-02-26 7:29 ` Christophe Leroy
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=237d8319-8127-c0fe-a855-ca04408bc925@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=ajd@linux.ibm.com \
--cc=dja@axtens.net \
--cc=jniethe5@gmail.com \
--cc=joel@jms.id.au \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=ruscur@russell.cc \
/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