From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alvaro Neira Ayuso <alvaroneay@gmail.com>
Cc: netfilter-devel@vger.kernel.org, kaber@trash.net
Subject: Re: [nft PATCH 1/4] evaluate: refactor function to check the reject family in inet and bridge
Date: Tue, 21 Oct 2014 10:45:08 +0200 [thread overview]
Message-ID: <20141021084508.GA4728@salvia> (raw)
In-Reply-To: <1413847780-10149-1-git-send-email-alvaroneay@gmail.com>
On Tue, Oct 21, 2014 at 01:29:37AM +0200, Alvaro Neira Ayuso wrote:
> This patch make a refactorization of the code to check the reject family in inet
> and bridge. These changes will be used in follow up patches.
>
> Signed-off-by: Alvaro Neira Ayuso <alvaroneay@gmail.com>
> ---
> src/evaluate.c | 110 ++++++++++++++++++++++++++++++++------------------------
> 1 file changed, 63 insertions(+), 47 deletions(-)
>
> diff --git a/src/evaluate.c b/src/evaluate.c
> index 1fec120..977df86 100644
> --- a/src/evaluate.c
> +++ b/src/evaluate.c
> @@ -1202,12 +1202,72 @@ static int stmt_reject_gen_dependency(struct eval_ctx *ctx, struct stmt *stmt,
> return 0;
> }
>
> -static int stmt_evaluate_reject_family(struct eval_ctx *ctx, struct stmt *stmt,
> +static int stmt_evaluate_reject_inet(struct eval_ctx *ctx, struct stmt *stmt,
> + struct expr *expr)
> +{
> + const struct proto_desc *desc, *base;
> + int protocol;
> +
> + base = ctx->pctx.protocol[PROTO_BASE_LL_HDR].desc;
This base pointer is fetched, but you only need this if desc != NULL.
Please, while you're refactoring this, it's good if you avoid this.
> + desc = ctx->pctx.protocol[PROTO_BASE_NETWORK_HDR].desc;
> + if (desc != NULL) {
>From here:
> + protocol = proto_find_num(base, desc);
> + switch (protocol) {
> + case NFPROTO_IPV4:
> + if (stmt->reject.family == NFPROTO_IPV4)
> + return 0;
> + return stmt_error(ctx, stmt,
> + "conflicting protocols specified: ip vs ip6");
> + case NFPROTO_IPV6:
> + if (stmt->reject.family == NFPROTO_IPV6)
> + return 0;
> + return stmt_error(ctx, stmt,
> + "conflicting protocols specified: ip vs ip6");
> + default:
> + BUG("unsupported family");
> + }
> + }
to there. You can put this code in another function, given that you'll
need it again for your patch 3/4.
static int stmt_evaluate_reject_inet_family(...)
{
int protocol;
protocol = proto_find_num(base, desc);
switch (protocol) {
case NFPROTO_IPV4:
if (stmt->reject.family != NFPROTO_IPV4)
return -1;
break;
case NFPROTO_IPV6:
if (stmt->reject.family == NFPROTO_IPV6)
return -1;
break;
default:
BUG("unsupported family");
}
return 0;
}
Then, from stmt_evaluate_reject_inet():
if (desc != NULL &&
stmt_evaluate_reject_inet_family(...) < 0)
return stmt_error(..., "conflicting protocols...");
> + if (stmt->reject.type == NFT_REJECT_ICMPX_UNREACH)
> + return 0;
> + if (stmt_reject_gen_dependency(ctx, stmt, expr) < 0)
> + return -1;
> + return 0;
> +}
> +
> +static int stmt_evaluate_reject_bridge(struct eval_ctx *ctx, struct stmt *stmt,
> struct expr *expr)
Same thing for the bridge code.
prev parent reply other threads:[~2014-10-21 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 23:29 [nft PATCH 1/4] evaluate: refactor function to check the reject family in inet and bridge Alvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 2/4] evaluate: accept a reject reason with incorrect network context Alvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 3/4] evaluate: no check the network context in reject with tcp reset reason Alvaro Neira Ayuso
2014-10-21 7:55 ` Pablo Neira Ayuso
2014-10-21 12:32 ` Álvaro Neira Ayuso
2014-10-20 23:29 ` [nft PATCH 4/4 v3] evaluate: fix a crash if we check the transport protocol is tcp Alvaro Neira Ayuso
2014-10-21 8:15 ` Pablo Neira Ayuso
2014-10-21 12:28 ` Álvaro Neira Ayuso
2014-10-21 8:45 ` Pablo Neira Ayuso [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=20141021084508.GA4728@salvia \
--to=pablo@netfilter.org \
--cc=alvaroneay@gmail.com \
--cc=kaber@trash.net \
--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 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.