public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] kernel: enable page poisoning on x86_64
Date: Tue, 14 Apr 2020 15:54:08 +0100	[thread overview]
Message-ID: <8305EFA8-F4F4-4194-8D74-88E3EFD377CD@ipfire.org> (raw)
In-Reply-To: <bbc1a44e-fc2c-944d-316a-6ed4af8ddca6@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]

Hey,

> On 14 Apr 2020, at 15:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello Michael,
> 
> possibly, but I consider this as being too important in order to drop it due
> to performance concerns. CONFIG_PAGE_POISONING_NO_SANITY reduces some performance
> overhead of page poisoning, but since this is currently not enabled on i586,
> I did not use in on x86_64, either.

Hmm, I am really not happy with such inconsistent configurations across multiple architectures.

This is either a feature that we want or not, but we do not want it on one platform and not on the other.

Although I would consider the performance overhead on x86_64 much smaller than i586. PAE might have the same advantage than x86_64.

> As mentioned, this is active on i586 already and I have not heard of IPFire
> being unusable on that architecture. :-)

Well, let’s say it is not running that well any more.

-Michael

> 
> Thanks, and best regards,
> Peter Müller
> 
>> Hi,
>> 
>> Can you perform any performance benchmarks to see how much this impacts IPsec and IPS throughput?
>> 
>> -Michael
>> 
>>> On 14 Apr 2020, at 15:32, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>> 
>>> This is already active on i586 and prevents information leaks from freed
>>> data.
>>> 
>>> Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
>>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>>> ---
>>> config/kernel/kernel.config.x86_64-ipfire | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
>>> index b16d13504..f6819859d 100644
>>> --- a/config/kernel/kernel.config.x86_64-ipfire
>>> +++ b/config/kernel/kernel.config.x86_64-ipfire
>>> @@ -6387,7 +6387,9 @@ CONFIG_DEBUG_KERNEL=y
>>> #
>>> # CONFIG_PAGE_EXTENSION is not set
>>> # CONFIG_DEBUG_PAGEALLOC is not set
>>> -# CONFIG_PAGE_POISONING is not set
>>> +CONFIG_PAGE_POISONING=y
>>> +# CONFIG_PAGE_POISONING_NO_SANITY is not set
>>> +CONFIG_PAGE_POISONING_ZERO=y
>>> # CONFIG_DEBUG_PAGE_REF is not set
>>> # CONFIG_DEBUG_RODATA_TEST is not set
>>> # CONFIG_DEBUG_OBJECTS is not set
>>> -- 
>>> 2.16.4
>> 


  reply	other threads:[~2020-04-14 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 14:32 Peter Müller
2020-04-14 14:33 ` Michael Tremer
2020-04-14 14:36   ` Peter Müller
2020-04-14 14:54     ` Michael Tremer [this message]
2020-04-14 15:04       ` Peter Müller

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=8305EFA8-F4F4-4194-8D74-88E3EFD377CD@ipfire.org \
    --to=michael.tremer@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