linux-kernel - Re: [PATCH v03 00/98] Userspace compile test and fixes for exported uapi header files

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]

Date:	Sat, 30 May 2015 22:12:48 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Mikko Rapeli <mikko.rapeli@....fi>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v03 00/98] Userspace compile test and fixes for exported
 uapi header files

On Sat, May 30, 2015 at 5:37 PM, Mikko Rapeli <mikko.rapeli@....fi> wrote:
> v3:
> tried to fix all v2 review findings
> tried to guess how to fix a few more issue
> with a few hacks, 0 files fail and 760 files pass the compile test on 32bit x86
>
> v2:
> https://lkml.org/lkml/2015/2/16/521
> added cross compiler support with CROSS_COMPILE,
> detecting libc and GCC headers from compiler,
> more header file fixes
>
> v1:
> https://lkml.org/lkml/2014/8/21/665
>
> Users of kernel header files would be happier if they did not contain
> kernel specific parts and would contain #include statements for all
> other header files that they depend on, and in general would compile.

Maybe this is a stupid question, but does that mean that many of our uapi
headers never worked as expected and don't build at all?

-- 
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/