linux-kernel - Re: using kernel headers in libc 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a36005b50911300943i947c91fva2b93f5f067665a1@mail.gmail.com>
Date:	Mon, 30 Nov 2009 09:43:49 -0800
From:	Ulrich Drepper <drepper@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: using kernel headers in libc headers

On Mon, Nov 30, 2009 at 09:01, H. Peter Anvin <hpa@...or.com> wrote:
> A better way is to factor out subsets; if <linux/sched.h> has too many
> things, we can break out the POSIX parts into <linux/sched_posix.h> or
> (certainly better if we have more than one of these)
> <linux/sched/posix.h> which can also be included by <linux/sched.h>.

This is at least as undesirable.

First, there can be several different of those.  E.g., there are
different levels of POSIX compliance and the number of growing.  There
are also conditions like

  if POSIX version > 2001012 || GNU source

How do you express this?

Second, it makes it hard to impossible for developers to use the
headers as part of the system documentation.  Many people (me
included) look at headers and the included comments.  With your scheme
the set of definitions (e.g., SCHED_* macros) might be spread out over
several different headers.  Currently they are all nicely group (in
the kernel and libc headers) and people can see what is available.

None of the #ifdefs should interfere with kernel compilation.  It can
be easily arranged so that when compiling the kernel all these macros
are automatically set.
--
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/