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:   Sun, 29 Jan 2017 18:13:36 +0100
From:   Sam Ravnborg <>
To:     Ingo Molnar <>
        Andrew Morton <>,
        Andy Lutomirski <>,
        Borislav Petkov <>,
        "H . Peter Anvin" <>,
        Linus Torvalds <>,
        Peter Zijlstra <>,
        Thomas Gleixner <>,
        Yinghai Lu <>
Subject: Re: [PATCH 01/50] x86/boot/e820: Introduce

On Sat, Jan 28, 2017 at 11:11:22PM +0100, Ingo Molnar wrote:
> The plan is to keep the old UAPI header in place but the kernel won't
> use it anymore - and after some time we'll try to remove it. (User-space
> tools better have local copies of headers anyway, instead of relying
> on kernel headers.)

The idea with uapi is the the kernel provides a sane set of headers
to be used by user space.
So we avoid random copies that is maintained by random people in random
ways resulting in random bugs.

The step(s) outlined here can only result in inconsistency and
cannot benefit neither user space nor the kernel in the long run.

The uapi shall be lean and clean headers, and shall include
no info whatsoever that is not relevant for user space.

But requiring all user space programs (diverse libc variants,
other programs) to maintain their own copy can only result in
inconsistencies that is the benefit for no one.


Powered by blists - more mailing lists