From: Michal Marek <mmarek@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: `make headers_check' bustage
Date: Tue, 12 Jul 2011 16:04:55 +0200 [thread overview]
Message-ID: <4E1C5487.9030405@suse.cz> (raw)
In-Reply-To: <20110707171627.4f15035e.akpm@linux-foundation.org>
On 8.7.2011 02:16, Andrew Morton wrote:
> It is just me, or is headers_check busted in current -linus?
>
> z:/usr/src/25> make mrproper; make allmodconfig; make headers_check
> ...
> /usr/src/25/usr/include/linux/kernel.h:65: userspace cannot reference function or variable defined in the kernel
Introduced by 7ef88ad5 (BUILD_BUG_ON: make it handle more cases), the
whole BUILD_BUG_ON stuff should be hidden behind #ifdef __KERNEL__, but
it's pretty harmless.
> /usr/src/25/usr/include/linux/quota.h:175: userspace cannot reference function or variable defined in the kernel
That's actualy a false positive, the header defines a prototype for the
quotactl() syscall.
> /usr/src/25/usr/include/linux/sdla.h:116: userspace cannot reference function or variable defined in the kernel
That looks indeed bogus, there is no sdla() syscall.
> /usr/src/25/usr/include/linux/soundcard.h:1054: userspace cannot reference function or variable defined in the kernel
As Vitaliy wrote, this is a leftover after 43a9907.
Nevertheless, these errors are pretty harmless, the prototypes do not
break parsing the header when compiling userspace programs.
Michal
next prev parent reply other threads:[~2011-07-12 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 0:16 `make headers_check' bustage Andrew Morton
2011-07-08 12:54 ` Vitaliy Ivanov
2011-07-12 14:04 ` Michal Marek [this message]
2011-07-12 16:01 ` Andrew Morton
2011-07-12 16:34 ` Michal Marek
2011-07-17 21:47 ` Randy Dunlap
2011-07-20 9:26 ` Vitaliy Ivanov
2011-07-20 9:30 ` Michal Marek
2011-07-20 9:36 ` Vitaliy Ivanov
2011-07-20 9:43 ` Michal Marek
2011-07-20 15:24 ` Andrew Morton
2011-07-21 5:15 ` Américo Wang
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=4E1C5487.9030405@suse.cz \
--to=mmarek@suse.cz \
--cc=akpm@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.