From: Giuseppe Longo <giuseppelng@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Giuseppe Longo <giuseppelng@gmail.com>
Subject: [iptables-compat PATCH 3/3] nft-ipv46: replace offset var with ctx->payload.offset
Date: Thu, 16 Oct 2014 16:29:53 +0200 [thread overview]
Message-ID: <1413469793-21382-3-git-send-email-giuseppelng@gmail.com> (raw)
In-Reply-To: <1413469793-21382-1-git-send-email-giuseppelng@gmail.com>
The offset variable (undefined) is passed to DEBUGP function,
so you get a compilation error if you try to build iptables
with debug enabled
Signed-off-by: Giuseppe Longo <giuseppelng@gmail.com>
---
iptables/nft-ipv4.c | 2 +-
iptables/nft-ipv6.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/iptables/nft-ipv4.c b/iptables/nft-ipv4.c
index eedcb50..a2c5806 100644
--- a/iptables/nft-ipv4.c
+++ b/iptables/nft-ipv4.c
@@ -205,7 +205,7 @@ static void nft_ipv4_parse_payload(struct nft_xt_ctx *ctx,
cs->fw.ip.invflags |= IPT_INV_FRAG;
break;
default:
- DEBUGP("unknown payload offset %d\n", offset);
+ DEBUGP("unknown payload offset %d\n", ctx->payload.offset);
break;
}
}
diff --git a/iptables/nft-ipv6.c b/iptables/nft-ipv6.c
index 2e50627..5489398 100644
--- a/iptables/nft-ipv6.c
+++ b/iptables/nft-ipv6.c
@@ -142,7 +142,7 @@ static void nft_ipv6_parse_payload(struct nft_xt_ctx *ctx,
if (inv)
cs->fw6.ipv6.invflags |= IPT_INV_PROTO;
default:
- DEBUGP("unknown payload offset %d\n", offset);
+ DEBUGP("unknown payload offset %d\n", ctx->payload.offset);
break;
}
}
--
1.9.1
next prev parent reply other threads:[~2014-10-16 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 14:29 [iptables-compat PATCH 1/3] ebtables-compat: fix print_header Giuseppe Longo
2014-10-16 14:29 ` [iptables-compat PATCH 2/3] nft: fix syntax error Giuseppe Longo
2014-10-20 9:01 ` Pablo Neira Ayuso
2014-10-16 14:29 ` Giuseppe Longo [this message]
2014-10-20 9:02 ` [iptables-compat PATCH 3/3] nft-ipv46: replace offset var with ctx->payload.offset Pablo Neira Ayuso
2014-10-20 9:01 ` [iptables-compat PATCH 1/3] ebtables-compat: fix print_header Pablo Neira Ayuso
2014-10-20 9:04 ` Pablo Neira Ayuso
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=1413469793-21382-3-git-send-email-giuseppelng@gmail.com \
--to=giuseppelng@gmail.com \
--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).