linux-kernel - Re: [tip:x86/mm] x86/boot/compressed/64: Describe the logic behind the LA57 check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 12 Mar 2018 09:42:27 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        "Kirill A. Shutemov" <kirill@...temov.name>,
        Peter Zijlstra <peterz@...radead.org>,
        Cyrill Gorcunov <gorcunov@...nvz.org>,
        Andy Lutomirski <luto@...capital.net>,
        Kees Cook <keescook@...omium.org>,
        Matthew Wilcox <willy@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Borislav Petkov <bp@...e.de>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Peter Anvin <hpa@...or.com>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        Jürgen Groß <jgross@...e.com>,
        linux-tip-commits@...r.kernel.org,
        Dave Hansen <dave.hansen@...el.com>
Subject: Re: [tip:x86/mm] x86/boot/compressed/64: Describe the logic behind
 the LA57 check

On Mon, Mar 12, 2018 at 7:50 AM, Kirill A. Shutemov
<kirill.shutemov@...ux.intel.com> wrote:
>
> I disagree that we should decide usefulness of the 5-level paging based on
> size of physical memory on the machine.
>
> Consider use case when you have 100TiB database file. It's pretty
> reasonable to mmap() such file at once even if you don't have 100TiB of
> physical memory to back it up. 1/100 of the file size may still work
> fairly well.
>
> Virtual address space is useful on its own and we shouldn't take the
> value from the user just because he doesn't have tens of terabytes of
> memory.

Absolutely.

Also, I'd suggest enabling 5-level paging as aggressively as possible
by default (ie whenever the hardware supports it), just for test
coverage.

Maybe in a year or two, when we actually have a fair amount of
coverage, we'll then say "ok, this just hurts normal workstations that
have the capability but only have ridiculously small fraction of
memory", and at that point say that unless you have a ton of RAM we'll
default to 4-level.

               Linus