From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, jeremy.fitzhardinge@citrix.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH] x86/mm: Use strtobool for noexec parsing
Date: Sun, 27 Feb 2022 20:13:56 +0000 [thread overview]
Message-ID: <20220227201356.241452-1-linux@treblig.org> (raw)
Use strtobool to parse the 'noexec' parameter rather than open coding
it.
'disable_nx' is changed to a bool and flipped to 'enable_nx'
so it's meaning follows the command line option.
There's no change in behaviour for noexec=on/off.
noexec=junk will now warn
strtobool allows 0/1 and y/n (etc) as well as the on/off.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
arch/x86/mm/setup_nx.c | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/arch/x86/mm/setup_nx.c b/arch/x86/mm/setup_nx.c
index ed5667f5169ff..77450b5889a0d 100644
--- a/arch/x86/mm/setup_nx.c
+++ b/arch/x86/mm/setup_nx.c
@@ -7,7 +7,7 @@
#include <asm/proto.h>
#include <asm/cpufeature.h>
-static int disable_nx;
+static bool enable_nx = true;
/*
* noexec = on|off
@@ -19,21 +19,15 @@ static int disable_nx;
*/
static int __init noexec_setup(char *str)
{
- if (!str)
- return -EINVAL;
- if (!strncmp(str, "on", 2)) {
- disable_nx = 0;
- } else if (!strncmp(str, "off", 3)) {
- disable_nx = 1;
- }
+ int ret = strtobool(str, &enable_nx);
x86_configure_nx();
- return 0;
+ return ret;
}
early_param("noexec", noexec_setup);
void x86_configure_nx(void)
{
- if (boot_cpu_has(X86_FEATURE_NX) && !disable_nx)
+ if (boot_cpu_has(X86_FEATURE_NX) && enable_nx)
__supported_pte_mask |= _PAGE_NX;
else
__supported_pte_mask &= ~_PAGE_NX;
@@ -46,7 +40,7 @@ void __init x86_report_nx(void)
"missing in CPU!\n");
} else {
#if defined(CONFIG_X86_64) || defined(CONFIG_X86_PAE)
- if (disable_nx) {
+ if (!enable_nx) {
printk(KERN_INFO "NX (Execute Disable) protection: "
"disabled by kernel command line option\n");
} else {
--
2.35.1
next reply other threads:[~2022-02-27 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 20:13 Dr. David Alan Gilbert [this message]
2022-03-02 12:14 ` [PATCH] x86/mm: Use strtobool for noexec parsing Borislav Petkov
2022-03-02 14:19 ` Dr. David Alan Gilbert
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=20220227201356.241452-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=dave.hansen@linux.intel.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.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