linux-kernel - just how "sanitized" are the sanitized 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-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0611291812510.7515@localhost.localdomain>
Date:	Wed, 29 Nov 2006 18:15:40 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: just how "sanitized" are the sanitized headers?

  i noticed that, when i generate the sanitized headers with "make
headers_install", there are still a number of headers files that are
installed with variations on "#ifdef __KERNEL__".

  i always thought the fundamental property of sanitized headers was
to be compatible with glibc and have no traces of "KERNEL" content
left.  so what's the purpose of leaving some header files with that
preprocessor content?  thanks.

rday
-
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/