From: Flavio Leitner <fbl@sysclose.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netdev@vger.kernel.org, Joe Stringer <joe@ovn.org>,
Pravin B Shelar <pshelar@ovn.org>,
dev@openvswitch.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next 1/8] netfilter: use macros to create module aliases.
Date: Thu, 11 Apr 2019 15:33:42 -0300 [thread overview]
Message-ID: <20190411183342.GA21048@p50.lan> (raw)
In-Reply-To: <20190331220743.uwlpdr77cpuhh7fb@salvia>
On Mon, Apr 01, 2019 at 12:07:43AM +0200, Pablo Neira Ayuso wrote:
> On Tue, Mar 26, 2019 at 05:57:08PM -0300, Flavio Leitner wrote:
> > Each NAT helper creates a module alias which follows a pattern.
> > Use macros for consistency.
> >
> > Signed-off-by: Flavio Leitner <fbl@sysclose.org>
> > ---
> > include/net/netfilter/nf_conntrack_helper.h | 4 ++++
> > net/ipv4/netfilter/nf_nat_h323.c | 2 +-
> > net/ipv4/netfilter/nf_nat_pptp.c | 2 +-
> > net/netfilter/nf_nat_amanda.c | 2 +-
> > net/netfilter/nf_nat_ftp.c | 2 +-
> > net/netfilter/nf_nat_irc.c | 2 +-
> > net/netfilter/nf_nat_sip.c | 2 +-
> > net/netfilter/nf_nat_tftp.c | 2 +-
> > 8 files changed, 11 insertions(+), 7 deletions(-)
> >
> > diff --git a/include/net/netfilter/nf_conntrack_helper.h b/include/net/netfilter/nf_conntrack_helper.h
> > index ec52a8dc32fd..e86fadf7e7c5 100644
> > --- a/include/net/netfilter/nf_conntrack_helper.h
> > +++ b/include/net/netfilter/nf_conntrack_helper.h
> > @@ -15,6 +15,10 @@
> > #include <net/netfilter/nf_conntrack_extend.h>
> > #include <net/netfilter/nf_conntrack_expect.h>
> >
> > +#define NF_CT_NAT_HELPER_MOD_NAME(name) "ip_nat_" name
>
> I'd suggest a rename from NF_CT_NAT_HELPER_MOD_NAME() to
> NF_NAT_HELPER_NAME().
OK.
> Please, also use "nf_nat_" prefix instead, "ip_nat" is legacy stuff.
I don't think we can, because people might be using
the current alias which is ip_nat_something. This patch
is just making it more robust.
> > +#define MODULE_ALIAS_NFCT_HELPER_NAT(name) \
> > + MODULE_ALIAS(NF_CT_NAT_HELPER_MOD_NAME(name))
>
> Probably:
>
> MODULE_ALIAS_NF_NAT_HELPER
>
> instead of MODULE_ALIAS_NFCT_HELPER_NAT.
OK.
fbl
next prev parent reply other threads:[~2019-04-11 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 20:57 [PATCH net-next 0/8] openvswitch: load and reference the NAT helper Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 1/8] netfilter: use macros to create module aliases Flavio Leitner
2019-03-31 22:07 ` Pablo Neira Ayuso
2019-04-11 18:33 ` Flavio Leitner [this message]
2019-03-26 20:57 ` [PATCH net-next 2/8] netfilter: add API to manage NAT helpers Flavio Leitner
2019-03-31 22:10 ` Pablo Neira Ayuso
2019-04-11 18:35 ` Flavio Leitner
2019-03-31 22:12 ` Pablo Neira Ayuso
2019-03-26 20:57 ` [PATCH net-next 3/8] netfilter: nf_nat: register amanda NAT helper Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 4/8] netfilter: nf_nat: register ftp " Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 5/8] netfilter: nf_nat: register irc " Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 6/8] netfilter: nf_nat: register sip " Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 7/8] netfilter: nf_nat: register tftp " Flavio Leitner
2019-03-26 20:57 ` [PATCH net-next 8/8] openvswitch: load and reference the " Flavio Leitner
2019-03-28 23:55 ` [PATCH net-next 0/8] " David Miller
2019-03-31 20:56 ` David Miller
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=20190411183342.GA21048@p50.lan \
--to=fbl@sysclose.org \
--cc=dev@openvswitch.org \
--cc=joe@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pshelar@ovn.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).