linux-kernel - Re: Official Linux system wrapper library?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a67f4f9c-701f-f607-e708-b8545d80549e@infradead.org>
Date:   Mon, 12 Nov 2018 10:14:26 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Joseph Myers <joseph@...esourcery.com>,
        Greg KH <gregkh@...uxfoundation.org>
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 11/12/18 10:09 AM, Joseph Myers wrote:
> On Mon, 12 Nov 2018, Greg KH wrote:
> 
>> If there are still problems with this, please let us know and we will be
>> glad to resolve them.
> 
> With headers installed from Linus's latest tree, I retried (for x86_64) 
> the case of a source file containing the single line
> 
> #include <linux/elfcore.h>
> 
> which (as previously discussed, and Arnd had an RFC patch) I want to use 
> in a glibc test of header consistency.  It gives errors "unknown type name 
> 'elf_greg_t'" etc. (for lots more types as well) - but even before getting 
> onto those errors, there's
> 
> asm/signal.h:127:2: error: unknown type name 'size_t'
> 
> from a header included from linux/elfcore.h.  So this doesn't seem to be 
> working as I'd expect yet.


Yes, someone from Google (iirc) and also David Howells had some tests
that would point out all of the problems.  I thought (expected) more follow-up
from them with patches...


-- 
~Randy