From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Russell Currey <ruscur@russell.cc>
Cc: kernel-hardening@lists.openwall.com, npiggin@gmail.com,
dja@axtens.net, ajd@linux.ibm.com, joel@jms.id.au,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 3/5] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime
Date: Tue, 07 Jan 2020 21:48:33 +1100 [thread overview]
Message-ID: <87r20b1r0e.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20191231181413.Horde.DSSo7dOhVEixKzJ75Uu9ZA1@messagerie.si.c-s.fr>
Christophe Leroy <christophe.leroy@c-s.fr> writes:
> Russell Currey <ruscur@russell.cc> a écrit :
>
>> Very rudimentary, just
>>
>> echo 1 > [debugfs]/check_wx_pages
>>
>> and check the kernel log. Useful for testing strict module RWX.
>
> For testing strict module RWX you could instead implement
> module_arch_freeing_init() and call ptdump_check_wx() from there.
That could get expensive on large systems, not sure if we want it
enabled by default?
cheers
>> diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug
>> index 4e1d39847462..7c14c9728bc0 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
>> 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 2f9ddc29c535..b6cba29ae4a0 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.
>> @@ -409,6 +409,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.24.1
next prev parent reply other threads:[~2020-01-07 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 5:55 [PATCH v6 0/5] Implement STRICT_MODULE_RWX for powerpc Russell Currey
2019-12-24 5:55 ` [PATCH v6 1/5] powerpc/mm: Implement set_memory() routines Russell Currey
2020-01-08 12:52 ` Christophe Leroy
2020-02-03 0:46 ` Russell Currey
2020-02-03 7:06 ` Christophe Leroy
2020-01-20 8:35 ` Christophe Leroy
2019-12-24 5:55 ` [PATCH v6 2/5] powerpc/kprobes: Mark newly allocated probes as RO Russell Currey
2020-01-08 16:48 ` Christophe Leroy
2019-12-24 5:55 ` [PATCH v6 3/5] powerpc/mm/ptdump: debugfs handler for W+X checks at runtime Russell Currey
2019-12-31 17:14 ` Christophe Leroy
2020-01-07 10:48 ` Michael Ellerman [this message]
2019-12-24 5:55 ` [PATCH v6 4/5] powerpc: Set ARCH_HAS_STRICT_MODULE_RWX Russell Currey
2019-12-24 5:55 ` [PATCH v6 5/5] powerpc/configs: Enable STRICT_MODULE_RWX in skiroot_defconfig Russell Currey
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=87r20b1r0e.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ajd@linux.ibm.com \
--cc=christophe.leroy@c-s.fr \
--cc=dja@axtens.net \
--cc=joel@jms.id.au \
--cc=kernel-hardening@lists.openwall.com \
--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;
as well as URLs for NNTP newsgroup(s).