From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kernel: disable CONFIG_MODIFY_LDT_SYSCALL on i586 and x86_64
Date: Wed, 10 Jun 2020 10:26:38 +0200 [thread overview]
Message-ID: <43f88eef907afbc96ec3eb18a11af054@ipfire.org> (raw)
In-Reply-To: <62aee582-3d49-6662-9285-c9566c17575a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
This patch does nothing. Simply remove a CONFIG option will not disable
it
it will readded with the defconfig wich is "Y" by next make.
After change you should always run "make oldconfig" to check if the
change is valid or change other config that depend on this setting.
Arne
Am 2020-06-07 18:32, schrieb Peter Müller:
> Fixes: #12382
>
> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/kernel/kernel.config.i586-ipfire | 1 -
> config/kernel/kernel.config.x86_64-ipfire | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/config/kernel/kernel.config.i586-ipfire
> b/config/kernel/kernel.config.i586-ipfire
> index 0b6e0ca08..d21718829 100644
> --- a/config/kernel/kernel.config.i586-ipfire
> +++ b/config/kernel/kernel.config.i586-ipfire
> @@ -633,7 +633,6 @@ CONFIG_HOTPLUG_CPU=y
> # CONFIG_DEBUG_HOTPLUG_CPU0 is not set
> # CONFIG_COMPAT_VDSO is not set
> # CONFIG_CMDLINE_BOOL is not set
> -CONFIG_MODIFY_LDT_SYSCALL=y
> CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
>
> #
> diff --git a/config/kernel/kernel.config.x86_64-ipfire
> b/config/kernel/kernel.config.x86_64-ipfire
> index 27b073ec7..193c6e3a9 100644
> --- a/config/kernel/kernel.config.x86_64-ipfire
> +++ b/config/kernel/kernel.config.x86_64-ipfire
> @@ -650,7 +650,6 @@ CONFIG_HOTPLUG_CPU=y
> # CONFIG_LEGACY_VSYSCALL_EMULATE is not set
> CONFIG_LEGACY_VSYSCALL_NONE=y
> # CONFIG_CMDLINE_BOOL is not set
> -CONFIG_MODIFY_LDT_SYSCALL=y
> CONFIG_HAVE_LIVEPATCH=y
> # CONFIG_LIVEPATCH is not set
> CONFIG_ARCH_HAS_ADD_PAGES=y
prev parent reply other threads:[~2020-06-10 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 16:32 Peter Müller
2020-06-10 8:26 ` Arne Fitzenreiter [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=43f88eef907afbc96ec3eb18a11af054@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.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