All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Borislav Petkov <bp@alien8.de>
Cc: dave.hansen@linux.intel.com, luto@kernel.org,
	peterz@infradead.org, jeremy.fitzhardinge@citrix.com,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Use strtobool for noexec parsing
Date: Wed, 2 Mar 2022 14:19:12 +0000	[thread overview]
Message-ID: <Yh984FR4fd/cSlaS@gallifrey> (raw)
In-Reply-To: <Yh9ffhD3809qieua@nazgul.tnic>

* Borislav Petkov (bp@alien8.de) wrote:
> On Sun, Feb 27, 2022 at 08:13:56PM +0000, Dr. David Alan Gilbert wrote:
> > 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(-)
> 
> https://lkml.kernel.org/r/20220127115626.14179-6-bp@alien8.de

Oh well; good.

Thanks for the pointer.

Dave

> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

      reply	other threads:[~2022-03-02 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-27 20:13 [PATCH] x86/mm: Use strtobool for noexec parsing Dr. David Alan Gilbert
2022-03-02 12:14 ` Borislav Petkov
2022-03-02 14:19   ` Dr. David Alan Gilbert [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=Yh984FR4fd/cSlaS@gallifrey \
    --to=linux@treblig.org \
    --cc=bp@alien8.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.