From: Florian Westphal <fw@strlen.de>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: ebt_ip6: allow matching on ipv6-icmp types/codes
Date: Fri, 17 Dec 2010 17:21:10 +0100 [thread overview]
Message-ID: <20101217162110.GA9421@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <alpine.LNX.2.01.1012171654410.29660@obet.zrqbmnf.qr>
Jan Engelhardt <jengelh@medozas.de> wrote:
> On Friday 2010-12-17 16:27, Florian Westphal wrote:
> >
> >+++ ebt_ip6.c
> > if (info->bitmask & EBT_IP6_DPORT) {
> >- u32 dst = ntohs(pptr->dst);
> >+ u32 dst = ntohs(pptr->tcpudphdr.dst);
>
> The actual field however is smaller, so to me, this looks itching
> to be changed to
> uint16_t dst = ntohs(pptr->tcpudphdr.dst);
Indeed.
> >@@ -103,6 +115,14 @@ static int ebt_ip6_mt_check(const struct xt_mtchk_param *par)
> > return -EINVAL;
> > if (info->bitmask & EBT_IP6_SPORT && info->sport[0] > info->sport[1])
> > return -EINVAL;
> >+ if (info->bitmask & EBT_IP6_ICMP6) {
> >+ if ((info->invflags & EBT_IP6_PROTO ||
> >+ info->protocol != IPPROTO_ICMPV6))
> >+ return -EINVAL;
>
> Your parenthesis are a little out of balance, it's the & and | that
> are commonly guarded. That probably should have been:
>
> if ((info->invflags & EBT_IP6_PROTO) ||
> info->protocol != IPPROTO_ICMPV6)
Right.
> /* check other places too */
You are right,
If (foo & bar && baz)
is used in other places as well.
But I would prefer to keep cleanups and functional changes separated.
I will make the u16 and the () changes, however I'll wait a couple of
hours to give others time to speak up.
Thanks for reviewing.
Florian
next prev parent reply other threads:[~2010-12-17 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 15:27 [PATCH] netfilter: ebt_ip6: allow matching on ipv6-icmp types/codes Florian Westphal
2010-12-17 15:59 ` Jan Engelhardt
2010-12-17 16:21 ` Florian Westphal [this message]
2010-12-17 17:03 ` Jan Engelhardt
2010-12-18 16:33 ` Bart De Schuymer
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=20101217162110.GA9421@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=jengelh@medozas.de \
--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).