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]
Message-ID: <20181112175305.GB15484@kroah.com>
Date:   Mon, 12 Nov 2018 09:53:05 -0800
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Joseph Myers <joseph@...esourcery.com>
Cc:     Willy Tarreau <w@....eu>, Florian Weimer <fweimer@...hat.com>,
        "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
        Daniel Colascione <dancol@...gle.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Joel Fernandes <joelaf@...gle.com>,
        Linux API <linux-api@...r.kernel.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        Carlos O'Donell <carlos@...hat.com>,
        "libc-alpha@...rceware.org" <libc-alpha@...rceware.org>
Subject: Re: Official Linux system wrapper library?

On Mon, Nov 12, 2018 at 05:36:11PM +0000, Joseph Myers wrote:
> What *is*, in my view, a bug in the uapi headers is that some of them 
> don't work when included on their own.  I'd expect #include 
> <linux/whatever.h> or #include <asm/whatever.h>, for any such header 
> installed by make headers_install, to compile on its own in userspace 
> without needing any other headers to be included first, unless some header 
> is specifically defined as being an internal part of another header which 
> is the one that should be included.

Yes, that is a bug, and people have been working on fixing that.  We now
have a new build target:
	make headers_check
to keep this all working properly.

Right now on Linus's latest tree I only see one failure when running
this:
	./usr/include/linux/v4l2-controls.h:1105: found __[us]{8,16,32,64} type without #include <linux/types.h>
so we are getting better.

If there are still problems with this, please let us know and we will be
glad to resolve them.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ