All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: [PATCH 2.6.11 2/4]: fix iptables userspace build
Date: Fri, 04 Feb 2005 04:05:12 +0100	[thread overview]
Message-ID: <4202E668.6030005@trash.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Netfilter uses u_intXX_t types in it's headers shared with userspace. 
Some patch
added uXX types to a header, but iptables userspace doesn't know these 
types. This
breaks compilation with recent kernels. I know netfilter shouldn't use 
these types
in headers shared with userspace, but it currently does so in all files, 
so the
simple fix is to replace uXX by u_intXX_t.



[-- Attachment #2: 02.diff --]
[-- Type: text/x-patch, Size: 1007 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2005/02/01 14:16:17+01:00 pablo@eurodev.net 
#   [NETFILTER]: fix iptables userspace build
#   
#   Signed-off-by: Pablo Neira Ayuso <pablo@eurodev.net>
#   Signed-off-by: Patrick McHardy <kaber@trash.net>
# 
# include/linux/netfilter_ipv4/ip_conntrack_tuple.h
#   2005/02/01 14:16:09+01:00 pablo@eurodev.net +2 -2
#   [NETFILTER]: fix iptables userspace build
#   
#   Signed-off-by: Pablo Neira Ayuso <pablo@eurodev.net>
#   Signed-off-by: Patrick McHardy <kaber@trash.net>
# 
diff -Nru a/include/linux/netfilter_ipv4/ip_conntrack_tuple.h b/include/linux/netfilter_ipv4/ip_conntrack_tuple.h
--- a/include/linux/netfilter_ipv4/ip_conntrack_tuple.h	2005-02-03 20:43:01 +01:00
+++ b/include/linux/netfilter_ipv4/ip_conntrack_tuple.h	2005-02-03 20:43:01 +01:00
@@ -64,10 +64,10 @@
 		} u;
 
 		/* The protocol. */
-		u8 protonum;
+		u_int8_t protonum;
 
 		/* The direction (for tuplehash) */
-		u8 dir;
+		u_int8_t dir;
 	} dst;
 };
 

                 reply	other threads:[~2005-02-04  3:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4202E668.6030005@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=netfilter-devel@lists.netfilter.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.