From: "Gao Feng" <gfree.wind@foxmail.com>
To: "'Pablo Neira Ayuso'" <pablo@netfilter.org>
Cc: <netfilter-devel@vger.kernel.org>, <gfree.wind@gmail.com>
Subject: RE: [PATCH nf-next 1/4] netfilter: amanda: Correct the return value comparison of the func nf_nat_mangle_udp_packet
Date: Mon, 27 Mar 2017 20:48:57 +0800 [thread overview]
Message-ID: <000801d2a6f8$80709dd0$8151d970$@foxmail.com> (raw)
In-Reply-To: <20170327121232.GA15713@salvia>
> -----Original Message-----
> From: Pablo Neira Ayuso [mailto:pablo@netfilter.org]
> Sent: Monday, March 27, 2017 8:13 PM
> To: fgao@ikuai8.com
> Cc: netfilter-devel@vger.kernel.org; gfree.wind@gmail.com
> Subject: Re: [PATCH nf-next 1/4] netfilter: amanda: Correct the return
value
> comparison of the func nf_nat_mangle_udp_packet
>
> On Fri, Mar 17, 2017 at 02:47:19PM +0800, fgao@ikuai8.com wrote:
> > From: Gao Feng <fgao@ikuai8.com>
> >
> > The return value of nf_nat_mangle_udp_packet actually is 1 and 0 as
> > bool type. But the amanda codes compare it with NF_ACCEPT.
> >
> > Signed-off-by: Gao Feng <fgao@ikuai8.com>
> > ---
> > net/netfilter/nf_nat_amanda.c | 11 +++++------
> > 1 file changed, 5 insertions(+), 6 deletions(-)
> >
> > diff --git a/net/netfilter/nf_nat_amanda.c
> > b/net/netfilter/nf_nat_amanda.c index eb77238..e4d61a7 100644
> > --- a/net/netfilter/nf_nat_amanda.c
> > +++ b/net/netfilter/nf_nat_amanda.c
> > @@ -33,7 +33,6 @@ static unsigned int help(struct sk_buff *skb, {
> > char buffer[sizeof("65535")];
> > u_int16_t port;
> > - unsigned int ret;
> >
> > /* Connection comes from client. */
> > exp->saved_proto.tcp.port = exp->tuple.dst.u.tcp.port; @@ -63,14
> > +62,14 @@ static unsigned int help(struct sk_buff *skb,
> > }
> >
> > sprintf(buffer, "%u", port);
> > - ret = nf_nat_mangle_udp_packet(skb, exp->master, ctinfo,
> > - protoff, matchoff, matchlen,
> > - buffer, strlen(buffer));
> > - if (ret != NF_ACCEPT) {
> > + if (!nf_nat_mangle_udp_packet(skb, exp->master, ctinfo,
> > + protoff, matchoff, matchlen,
> > + buffer, strlen(buffer))) {
> > nf_ct_helper_log(skb, exp->master, "cannot mangle packet");
> > nf_ct_unexpect_related(exp);
> > + return NF_DROP;
> > }
> > - return ret;
> > + return NF_ACCEPT;
>
> This cleanup patches are a bit oversplit.
>
> Better, send one patch where you update nf_nat_mangle_udp_packet() and
> nf_nat_mangle_tcp_packet() to return boolean and update *all of the
netfilter
> spots* where we use them accordingly.
>
> Please be careful on this...
Ok, I would merge them into one patch.
I already checked them before, but I would check it again after merge.
Regards
Feng
next prev parent reply other threads:[~2017-03-27 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 6:45 [PATCH nf-next 0/4] Refine the nat helper codes fgao
2017-03-17 6:47 ` [PATCH nf-next 1/4] netfilter: amanda: Correct the return value comparison of the func nf_nat_mangle_udp_packet fgao
2017-03-27 12:12 ` Pablo Neira Ayuso
2017-03-27 12:48 ` Gao Feng [this message]
2017-03-17 6:47 ` [PATCH nf-next 2/4] netfilter: irc: Correct the return value comparison of the func nf_nat_mangle_tcp_packet fgao
2017-03-17 6:49 ` [PATCH nf-next 3/4] netfilter: helper: Use the bool instead of int type fgao
2017-03-17 6:49 ` [PATCH nf-next 4/4] netfilter: sip: Use NF_DROP and NF_ACCEPT instead of 0 and 1 fgao
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='000801d2a6f8$80709dd0$8151d970$@foxmail.com' \
--to=gfree.wind@foxmail.com \
--cc=gfree.wind@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 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).