Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1516546

Re: [kernel-hardening] Re: [PATCHv4 0/4] WX checking for arm64

From Ard Biesheuvel <ard.biesheuvel@linaro.org>
Newsgroups linux.kernel
Subject Re: [kernel-hardening] Re: [PATCHv4 0/4] WX checking for arm64
Date 2016-11-07 21:00 +0100
Message-ID <sAYff-7Eq-9@gated-at.bofh.it> (permalink)
References <swVIZ-4ii-7@gated-at.bofh.it> <sy5PY-1zc-5@gated-at.bofh.it> <sAUll-4ZD-39@gated-at.bofh.it> <sAYff-7Eq-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 7 November 2016 at 19:49, Mark Rutland <mark.rutland@arm.com> wrote:
> On Mon, Nov 07, 2016 at 03:38:02PM +0000, Mark Rutland wrote:
>> On Sun, Oct 30, 2016 at 03:03:07PM +0000, Catalin Marinas wrote:
>> > On Thu, Oct 27, 2016 at 09:27:30AM -0700, Laura Abbott wrote:
>> > > Laura Abbott (4):
>> > >   arm64: dump: Make ptdump debugfs a separate option
>> > >   arm64: dump: Make the page table dumping seq_file optional
>> > >   arm64: dump: Remove max_addr
>> > >   arm64: dump: Add checking for writable and exectuable pages
>> >
>> > Queued for 4.10. Thanks.
>>
>> Catalin mentioned to me that he saw some KASAN splats when testing; it
>> looks like need a fixup something like the below.
>
> As an aside, it looks like any ptdump usage when KASAN is enabled takes
> several minutes, which at boot time looks like a hang.
>
> AFAICT, this is because KASAN allocates *huge* VA ranges (4TB+) worth of
> zeroed shadow memory at pte granularity (reusing the same pmd, pud,
> tables), and the ptdump code dutifully walks this with, with the added
> KASAN instrumentation overhead.
>
> I'll try to dig into that tomorrow; I suspect/hope it's not necessary to
> keep all of that mapped.
>

I have noticed that in the past, but I see how this delay at boot time
is an issue. However, I don't think there is a huge cost involved in
terms of memory footprint: AFAIK, the same PMD/PTE/kasan zero page are
mapped over and over across the range.

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

[PATCHv4 0/4] WX checking for arm64 Laura Abbott <labbott@redhat.com> - 2016-10-27 18:30 +0200
  Re: [PATCHv4 0/4] WX checking for arm64 Catalin Marinas <catalin.marinas@arm.com> - 2016-10-30 22:30 +0100
    Re: [PATCHv4 0/4] WX checking for arm64 Mark Rutland <mark.rutland@arm.com> - 2016-11-07 16:50 +0100
      Re: [PATCHv4 0/4] WX checking for arm64 Laura Abbott <labbott@redhat.com> - 2016-11-07 17:30 +0100
        Re: [PATCHv4 0/4] WX checking for arm64 Catalin Marinas <catalin.marinas@arm.com> - 2016-11-07 17:40 +0100
      Re: [kernel-hardening] Re: [PATCHv4 0/4] WX checking for arm64 Mark Rutland <mark.rutland@arm.com> - 2016-11-07 21:00 +0100
        Re: [kernel-hardening] Re: [PATCHv4 0/4] WX checking for arm64 Ard Biesheuvel <ard.biesheuvel@linaro.org> - 2016-11-07 21:00 +0100

csiph-web