mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: christophe leroy <christophe.leroy@c-s.fr>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: Default to enabling STRICT_KERNEL_RWX
Date: Thu, 5 Oct 2017 20:57:24 +0200	[thread overview]
Message-ID: <e5dcb727-cd7a-0e19-cf9a-8d2e5dd5f258@c-s.fr> (raw)
In-Reply-To: <CAGXu5jLx+eMYrehvrT7+3V3Joa6VDAbhkLLDndC5aYLxJGmhYA@mail.gmail.com>



Le 05/10/2017 à 19:30, Kees Cook a écrit :
> On Thu, Oct 5, 2017 at 12:49 AM, Christophe LEROY
> <christophe.leroy@c-s.fr> wrote:
>>
>>
>> Le 05/10/2017 à 05:45, Kees Cook a écrit :
>>>
>>> When available, CONFIG_KERNEL_RWX should be default-enabled.
>>
>>
>> On PPC32, this option implies deactivating BATs and/or LTLB mapping of the
>> linear kernel address space, hence a significant performance degradation.
>>
>> So at least on PPC32, it should remain unselected by default.
> 
> Alright, sounds fine to me. Would this be okay?
> 
> +       select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT if !PPC64

You mean

select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT if PPC64

Don't you ?

Christophe

> 
> -Kees
> 
>>
>> Christophe
>>
>>
>>>
>>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>>> Cc: Paul Mackerras <paulus@samba.org>
>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>>> Cc: linuxppc-dev@lists.ozlabs.org
>>> Signed-off-by: Kees Cook <keescook@chromium.org>
>>> ---
>>>    arch/powerpc/Kconfig | 1 +
>>>    1 file changed, 1 insertion(+)
>>>
>>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>>> index 809c468edab1..9a549bbfc278 100644
>>> --- a/arch/powerpc/Kconfig
>>> +++ b/arch/powerpc/Kconfig
>>> @@ -178,6 +178,7 @@ config PPC
>>>          select HAVE_ARCH_TRACEHOOK
>>>          select ARCH_HAS_STRICT_KERNEL_RWX       if ((PPC_BOOK3S_64 ||
>>> PPC32) && !RELOCATABLE && !HIBERNATION)
>>>          select ARCH_OPTIONAL_KERNEL_RWX         if
>>> ARCH_HAS_STRICT_KERNEL_RWX
>>> +       select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
>>>          select HAVE_CBPF_JIT                    if !PPC64
>>>          select HAVE_CONTEXT_TRACKING            if PPC64
>>>          select HAVE_DEBUG_KMEMLEAK
>>>
>>
> 
> 
> 

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

  reply	other threads:[~2017-10-05 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  3:45 Kees Cook
2017-10-05  7:49 ` Christophe LEROY
2017-10-05 17:30   ` Kees Cook
2017-10-05 18:57     ` christophe leroy [this message]
2017-10-05 18:58       ` Kees Cook

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=e5dcb727-cd7a-0e19-cf9a-8d2e5dd5f258@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®