From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: whose job is it to include various header files?
Date: Thu, 13 Mar 2008 15:46:31 -0700 [thread overview]
Message-ID: <20080313154631.ae147130.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0803131802020.20317@localhost.localdomain>
On Thu, 13 Mar 2008 18:09:12 -0400 (EDT) Robert P. J. Day wrote:
>
> more a philosophy question than anything but, while poking around
> the percpu stuff today, i noticed in the header file linux/percpu.h
> the opening snippet:
>
> #include <linux/preempt.h>
> #include <linux/slab.h> /* For kmalloc() */
> #include <linux/smp.h>
> #include <linux/string.h> /* For memset() */
> #include <linux/cpumask.h>
> ...
>
> hmmm, i thought to myself (because that's how i refer to myself), i
> wonder why this header file is including headers for kmalloc() and
> memset() when this header file makes no reference to those routines.
> let's see what happens if i remove them and:
>
> $ make distclean
> $ make defconfig [x86]
> $ make
>
> ... chug chug chug ...
>
> CC arch/x86/kernel/nmi_32.o
> arch/x86/kernel/nmi_32.c: In function ‘check_nmi_watchdog’:
> arch/x86/kernel/nmi_32.c:81: error: implicit declaration of function ‘kmalloc’
> arch/x86/kernel/nmi_32.c:81: error: ‘GFP_KERNEL’ undeclared (first use in this function)
> arch/x86/kernel/nmi_32.c:81: error: (Each undeclared identifier is reported only once
> arch/x86/kernel/nmi_32.c:81: error: for each function it appears in.)
> arch/x86/kernel/nmi_32.c:81: warning: assignment makes pointer from integer without a cast
> arch/x86/kernel/nmi_32.c:118: error: implicit declaration of function ‘kfree’
> make[1]: *** [arch/x86/kernel/nmi_32.o] Error 1
> make: *** [arch/x86/kernel] Error 2
> $
>
> ok, now i know. but that means, of course, that nmi_32.c is
> invoking kmalloc() without ever having included the necessary header
> file for it -- it's just inheriting that from linux/percpu.h.
>
> doesn't that (sort of) violate the kernel coding style? if a file
> somewhere needs the contents of some header file, isn't it that file's
> responsibility to explicitly include it, and not quietly realize it's
> getting it from elsewhere?
Yes.
---
~Randy
next prev parent reply other threads:[~2008-03-13 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 22:09 Robert P. J. Day
2008-03-13 22:46 ` Randy Dunlap [this message]
2008-03-13 23:53 ` Jesper Juhl
2008-03-14 1:02 ` Robert P. J. Day
2008-03-14 1:36 ` Jan Engelhardt
2008-03-14 1:53 ` Robert P. J. Day
2008-03-14 5:47 ` Alexey Dobriyan
2008-03-14 8:01 ` Robert P. J. Day
2008-03-14 6:47 ` mws
2008-03-14 8:07 ` Robert P. J. Day
2008-03-14 9:29 ` Robert P. J. Day
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=20080313154631.ae147130.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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
all inboxes | Powered by JetHome®