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:   Fri, 15 Dec 2017 18:52:43 -0800
From:   Linus Torvalds <>
To:     Al Viro <>
Cc:     Dave Hansen <>,
        Dan Williams <>,
        Peter Zijlstra <>,
        Linux Kernel Mailing List <>,
        Thomas Gleixner <>,
        "the arch/x86 maintainers" <>,
        Andy Lutomirsky <>,
        Borislav Petkov <>,
        Greg KH <>,
        Kees Cook <>,
        Hugh Dickins <>,
        Brian Gerst <>,
        Josh Poimboeuf <>,
        Denys Vlasenko <>,
        Boris Ostrovsky <>,
        Juergen Gross <>,
        David Laight <>,
        Eduardo Valentin <>,
        "Liguori, Anthony" <>,
        Will Deacon <>,
        linux-mm <>,
        "Kirill A. Shutemov" <>
Subject: Re: [PATCH v2 01/17] mm/gup: Fixup p*_access_permitted()

On Fri, Dec 15, 2017 at 6:48 PM, Al Viro <> wrote:
> Treating protection key bits as "escalate to page fault and let that
> deal with the checks" should be fine

Well, it's *semantically* fine and I think it's the right model from
that standpoint.

However, since the main use case of protection keys is probably
databases (Dave?) and since those also might be performance-sensitive
about direct-IO doing page table lookups, it might not be great in


Powered by blists - more mailing lists