From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Balazs Scheidler <bazsi@balabit.hu>,
KOVACS Krisztian <hidden@balabit.hu>,
Patrick McHardy <kaber@trash.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: tproxy: added IPv6 support to the socket match
Date: Thu, 28 Oct 2010 20:51:43 +0200 [thread overview]
Message-ID: <AANLkTi=KRAcoonwFHKNaptap2LQHDswRCGpect82aHzx@mail.gmail.com> (raw)
In-Reply-To: <201010231923.o9NJNK9U013494@hera.kernel.org>
On Sat, Oct 23, 2010 at 21:23, Linux Kernel Mailing List
<linux-kernel@vger.kernel.org> wrote:
> Gitweb: http://git.kernel.org/linus/b64c9256a9b76fc9f059f71bd08ba88fb0cbba2e
> Commit: b64c9256a9b76fc9f059f71bd08ba88fb0cbba2e
> Parent: 6ad7889327a5ee6ab4220bd34e4428c7d0de0f32
> Author: Balazs Scheidler <bazsi@balabit.hu>
> AuthorDate: Thu Oct 21 16:19:42 2010 +0200
> Committer: Patrick McHardy <kaber@trash.net>
> CommitDate: Thu Oct 21 16:19:42 2010 +0200
>
> tproxy: added IPv6 support to the socket match
>
> The ICMP extraction bits were contributed by Harry Mason.
>
> Signed-off-by: Balazs Scheidler <bazsi@balabit.hu>
> Signed-off-by: KOVACS Krisztian <hidden@balabit.hu>
> Signed-off-by: Patrick McHardy <kaber@trash.net>
> ---
> net/netfilter/xt_socket.c | 165 ++++++++++++++++++++++++++++++++++++++++++---
> 1 files changed, 154 insertions(+), 11 deletions(-)
>
> diff --git a/net/netfilter/xt_socket.c b/net/netfilter/xt_socket.c
> index 266faa0..2dbd4c8 100644
> --- a/net/netfilter/xt_socket.c
> +++ b/net/netfilter/xt_socket.c
> +static bool
> +socket_mt6_v1(const struct sk_buff *skb, struct xt_action_param *par)
> +{
> + struct ipv6hdr *iph = ipv6_hdr(skb);
> + struct udphdr _hdr, *hp = NULL;
> + struct sock *sk;
> + struct in6_addr *daddr, *saddr;
> + __be16 dport, sport;
> + int thoff;
> + u8 tproto;
tproto is unsigned...
> + const struct xt_socket_mtinfo1 *info = (struct xt_socket_mtinfo1 *) par->matchinfo;
> +
> + tproto = ipv6_find_hdr(skb, &thoff, -1, NULL);
but ipv6_find_hdr() returns int, and negative values for errors...
> + if (tproto < 0) {
which it can never catch.
> + pr_debug("unable to find transport header in IPv6 packet, dropping\n");
> + return NF_DROP;
> + }
net/netfilter/xt_socket.c:256: warning: comparison is always false due
to limited range of data type
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2010-10-28 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201010231923.o9NJNK9U013494@hera.kernel.org>
2010-10-28 18:51 ` Geert Uytterhoeven [this message]
2010-10-28 20:00 ` tproxy: added IPv6 support to the socket match David Miller
2010-10-29 14:31 ` Patrick McHardy
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='AANLkTi=KRAcoonwFHKNaptap2LQHDswRCGpect82aHzx@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bazsi@balabit.hu \
--cc=hidden@balabit.hu \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@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).