From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <garzik@havoc.gtf.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: Thu, 31 Jan 2002 12:51:50 +1100 [thread overview]
Message-ID: <7417.1012441910@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 30 Jan 2002 20:17:54 CDT." <20020130201754.B18730@havoc.gtf.org>
On Wed, 30 Jan 2002 20:17:54 -0500,
Jeff Garzik <garzik@havoc.gtf.org> wrote:
>On Thu, Jan 31, 2002 at 10:33:46AM +1100, Keith Owens wrote:
>> On Wed, 30 Jan 2002 13:24:22 -0500,
>> Pete Zaitcev <zaitcev@redhat.com> wrote:
>> >Kernel headers are not to be included in applications.
>>
>> Just to flog this dead horse into the ground, the reverse is also true.
>> Kernel code must not include user space headers (kernel code excludes
>> programs that are used to build the kernel).
>
>Wow, does that actually occur? File references?
It slips in occasionally. LVM in 2.4.0-test had #include <endian.h>, I
vaguely remember some compression code that included glibc headers by
mistake. We weed them out of the kernel whenever we spot them, they
tend not to live very long. Christoph Hellwig suggested a Makefile
change that prevents kernel code including user space headers, it is
included in kbuild 2.5 and there is a 2.4 version in
http://marc.theaimsgroup.com/?l=linux-kernel&m=100321690511549&w=2
next prev parent reply other threads:[~2002-01-31 1:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1012391761.28301.linux-kernel2news@redhat.com>
2002-01-30 18:24 ` Why 'linux/fs.h' cannot be included? I *can* Pete Zaitcev
2002-01-30 23:33 ` Keith Owens
2002-01-31 1:17 ` Jeff Garzik
2002-01-31 1:51 ` Keith Owens [this message]
2002-01-31 1:57 ` Jeff Garzik
2002-01-31 2:06 ` Keith Owens
2002-01-31 2:35 ` Jeff Garzik
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 10:20 DervishD
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51 ` Alan Cox
2002-01-29 14:42 ` Jeff Garzik
2002-01-28 19:31 DervishD
2002-01-28 19:44 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7417.1012441910@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=garzik@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox