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:   Mon, 16 Jan 2017 22:14:31 +0100 (CET)
From:   Thomas Gleixner <>
To:     David Smith <>
cc:     Peter Zijlstra <>,
        Linus Torvalds <>,
        Andy Lutomirski <>,
        Ingo Molnar <>,
        "H. Peter Anvin" <>,
        "" <>,
        "Frank Ch. Eigler" <>
Subject: Re: [RFC][PATCH] x86: Verify access_ok() context

On Mon, 16 Jan 2017, David Smith wrote:

> If you call access_ok() with page faulting disabled, you'll still see
> this new warning.

And how so? It's just checking for task context. page fault disable/enable
has absolutely nothing to do with that.

> If you put that new access_ok() call in a module that gets
> loaded/unloaded, you see one warning for every module load, which gets a
> bit annoying.

Can you please elaborate where this access_ok() is placed in the module



Powered by blists - more mailing lists