linux-kernel - Re: [PATCH] Drop an empty byteorder/generic.h from being exported to userspace.

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: <alpine.LFD.1.00.0804020656170.13637@localhost.localdomain>
Date:	Wed, 2 Apr 2008 07:00:32 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...shcourse.ca>
To:	Jiri Slaby <jirislaby@...il.com>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH] Drop an empty byteorder/generic.h from being exported
 to userspace.

On Wed, 2 Apr 2008, Jiri Slaby wrote:

> On 04/02/2008 03:38 AM, Robert P. J. Day wrote:
> > Since the entire meaningful contents of generic.h is wrapped by the
> > __KERNEL__ test, drop it from being passed to userspace, and remove
> > the now superfluous __KERNEL__ test.
> >
> > Signed-off-by: Robert P. J. Day <rpjday@...shcourse.ca>
> >
> > ---
> >
> >   is there some value in allowing an effectively empty header file to
> > be exported to userspace?
>
> Not breaking the userspace? The file is included in non-__KERNEL__
> sections from byteorder/*_endian.h.

ok ... and the value of including a completely empty header file is
... ?

rday
--


========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
--
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/