linux-kernel - Re: {PATCH] fix __packed in exported kernel headers

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] [day] [month] [year] [list]

Message-ID: <BANLkTimO0=V24FXYx4CEHTa6tLNB-0F-dQ@mail.gmail.com>
Date:	Thu, 30 Jun 2011 17:56:22 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Michal Marek <mmarek@...e.cz>, Joe Perches <joe@...ches.com>,
	Nick Bowler <nbowler@...iptictech.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
Subject: Re: {PATCH] fix __packed in exported kernel headers

On Thu, Jun 30, 2011 at 16:02, H. Peter Anvin wrote:
> On 06/30/2011 12:13 PM, Mike Frysinger wrote:
>>> Not unless the kernel uses its own namespace for these defines.  The
>>> thing is, most libraries have their own macro library for this, and
>>> collisions are both likely and bad.
>>
>> while that's true for exporting compiler.h, namespacing is irrelevant
>> to my requirement -- the headers should have sane/usable defaults.
>
> I have no idea what "your requirements" are

it's what ive already said and what you commented on multiple times.
exporting a header that cant be included directly without first
declaring some random set of defines is broken.

i'm not referring to some arbitrary set of requirements you may not know.

> but as someone who has
> actually implemented a C library on top of the Linux headers I can tell
> you it's a very real and relevant issue, and that it is historically one
> of the biggest problems.

no one said otherwise.  ive done quite a lot of work with uClibc, so
i'm familiar with the historical issues as well.
-mike
--
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/