From: Andrew Morton <akpm@osdl.org>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org, Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: [PATCH] 2.6.18-rc2-mm1: unresolved symbol brnf_deferred_hooks in xt_physdev module
Date: Fri, 28 Jul 2006 22:00:43 -0700 [thread overview]
Message-ID: <20060728220043.43201c6b.akpm@osdl.org> (raw)
In-Reply-To: <200607281338.22053.bero@arklinux.org>
On Fri, 28 Jul 2006 13:38:21 +0200
Bernhard Rosenkraenzer <bero@arklinux.org> wrote:
> The (trivial) patch below fixes the unresolved symbol brnf_deferred_hooks in
> the xt_physdev module in 2.6.18-rc2-mm1.
>
> Signed-off-by: Bernhard Rosenkraenzer <bero@arklinux.org>
>
> ---
> --- linux-2.6.17/net/netfilter/xt_physdev.c.ark 2006-07-28 13:34:31.000000000
> +0200
> +++ linux-2.6.17/net/netfilter/xt_physdev.c 2006-07-28 13:34:48.000000000
> +0200
> @@ -16,6 +16,8 @@
> #define MATCH 1
> #define NOMATCH 0
>
> +extern int brnf_deferred_hooks;
> +
> MODULE_LICENSE("GPL");
> MODULE_AUTHOR("Bart De Schuymer <bdschuym@pandora.be>");
> MODULE_DESCRIPTION("iptables bridge physical device match module");
OK, but please never put extern declarations in .c files. They need to go
in a header where the compiler can check that the variable's type is
consistent at all usage sites.
We already have such a declaration, so I guess this is the fix:
--- a/net/netfilter/xt_physdev.c~xt_physdev-build-fix
+++ a/net/netfilter/xt_physdev.c
@@ -10,6 +10,7 @@
#include <linux/module.h>
#include <linux/skbuff.h>
+#include <linux/netfilter/netfilter_bridge.h>
#include <linux/netfilter/xt_physdev.h>
#include <linux/netfilter/x_tables.h>
#include <linux/netfilter_bridge.h>
_
Your email client is wordwrapping patches, btw. There's a lot of it going
round at present.
prev parent reply other threads:[~2006-07-29 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 11:38 Bernhard Rosenkraenzer
2006-07-29 5:00 ` Andrew Morton [this message]
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=20060728220043.43201c6b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bdschuym@pandora.be \
--cc=bero@arklinux.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
Powered by JetHome