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  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, 1 May 2020 03:16:34 +0100
From:   Al Viro <>
        Andrew Morton <>,
        Christian Koenig <>,
        Huang Rui <>,
        Thomas Bogendoerfer <>,
        "James E.J. Bottomley" <>,
        Helge Deller <>,
        Benjamin Herrenschmidt <>,
        Paul Mackerras <>,
        "David S. Miller" <>,
        Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,, "H. Peter Anvin" <>,
        Dave Hansen <>,
        Andy Lutomirski <>,
        Peter Zijlstra <>,
        Chris Zankel <>,
        Max Filippov <>,
        Dan Williams <>,,,,,,,,,
Subject: Re: [PATCH V1 08/10] arch/kmap: Don't hard code kmap_prot values

On Thu, Apr 30, 2020 at 01:38:43PM -0700, wrote:
> From: Ira Weiny <>
> To support kmap_atomic_prot() on all architectures each arch must
> support protections passed in to them.
> Change csky, mips, nds32 and xtensa to use their global kmap_prot value
> rather than a hard coded value which was equal.

Minor nitpick: it's probably worth pointing out that kmap_prot on those
is a constant...

Powered by blists - more mailing lists