From: James Morris <jmorris@intercode.com.au>
To: Frank Davis <fdavis@si.rr.com>
Cc: linux-kernel@vger.kernel.org, Harald Welte <laforge@gnumonks.org>
Subject: [PATCH] Re: 2.5.32 : net/ipv4/netfilter/ipfwadm_core.c compile error
Date: Sun, 1 Sep 2002 13:18:32 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0209011232410.14016-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0208300801120.27846-100000@primetime>
On Fri, 30 Aug 2002, Frank Davis wrote:
> Hello all,
> While 'make modules', I received the following error.
>
> Regards,
> Frank
>
> ipfwadm_core.c: In function `ip_fw_chk':
> ipfwadm_core.c:450: structure has no member named `read_locked_map'
> ipfwadm_core.c:450: structure has no member named `write_locked_map'
Please see the fix below. (The problem only shows up when netfilter
debugging is enabled).
- James
--
James Morris
<jmorris@intercode.com.au>
diff -urN -X dontdiff linux-2.5.33.w1/net/ipv4/netfilter/ipfwadm_core.c linux-2.5.33.w1-ipfwadm/net/ipv4/netfilter/ipfwadm_core.c
--- linux-2.5.33.w1/net/ipv4/netfilter/ipfwadm_core.c Wed Aug 28 13:24:30 2002
+++ linux-2.5.33.w1-ipfwadm/net/ipv4/netfilter/ipfwadm_core.c Sun Sep 1 12:16:16 2002
@@ -156,7 +156,7 @@
#define dprint_ip(a)
#endif
-static rwlock_t ip_fw_lock = RW_LOCK_UNLOCKED;
+static DECLARE_RWLOCK(ip_fw_lock);
#if defined(CONFIG_IP_ACCT) || defined(CONFIG_IP_FIREWALL)
next prev parent reply other threads:[~2002-09-01 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 12:03 2.5.32 : net/ipv4/netfilter/ipfwadm_core.c compile error Frank Davis
2002-09-01 3:18 ` James Morris [this message]
2002-09-01 6:04 ` [PATCH] " David S. Miller
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=Mutt.LNX.4.44.0209011232410.14016-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=fdavis@si.rr.com \
--cc=laforge@gnumonks.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;
as well as URLs for NNTP newsgroup(s).