From: Arjan van de Ven <arjan@infradead.org>
To: Thierry Godefroy <thgodef@nerim.net>
Cc: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: Re: BUG in Linux 2.6.16/2.6.16.1 (compilation failure of third party software)
Date: Wed, 29 Mar 2006 06:42:31 +0200 [thread overview]
Message-ID: <1143607351.3049.4.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060329012122.0c533fc6.thgodef@nerim.net>
On Wed, 2006-03-29 at 01:21 +0200, Thierry Godefroy wrote:
> On Tue, 28 Mar 2006 17:51:11 -0500, Lee Revell wrote:
>
> > On Tue, 2006-03-28 at 20:29 +0200, Thierry Godefroy wrote:
> > > Paragon_NTFS_3.x.v5.1 fails to compile (with gcc v3.4.3) with the following
> > > errors:
> >
> > It's not a bug when an upgrade causes third party kernel modules not to
> > compile - your code needs to be updated to work with 2.6.16.
>
> Oh, yeah ?... Really ?... Please, read the errors before drawing hasted conclusions...
> The errors occur after the mere #inclusion of Linux headers. Here is a simple "code"
> which will trigger the error:
>
> #ifndef __KERNEL__
> #define __KERNEL__
> #endif
>
> #include <linux/module.h>
>
> int main() {
> return 0;
> }
>
> And I don't see anything wrong in that code...
then look again. Userspace that defines __KERNEL__ .... man that isn't
going ot work. __KERNEL__ is the ONLY safeguard we have to protect
userspace from miscompiling, and we highly assume userspace doesn't set
it. If this program does that then it really deserves all it gets.
next prev parent reply other threads:[~2006-03-29 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 18:29 Thierry Godefroy
2006-03-28 22:51 ` Lee Revell
2006-03-28 23:21 ` Thierry Godefroy
2006-03-29 4:42 ` Arjan van de Ven [this message]
[not found] <5Vr7d-4VR-15@gated-at.bofh.it>
2006-03-28 23:03 ` Robert Hancock
[not found] ` <5Vvkv-2MB-27@gated-at.bofh.it>
[not found] ` <5VvNw-3B1-3@gated-at.bofh.it>
2006-03-29 2:20 ` Robert Hancock
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=1143607351.3049.4.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=thgodef@nerim.net \
/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®