From: Flavio Leitner <fbl@redhat.com>
To: netdev@vger.kernel.org
Cc: Joe Stringer <joe@ovn.org>, Pravin B Shelar <pshelar@ovn.org>,
dev@openvswitch.org, netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH net-next v2 0/8] openvswitch: load and reference the NAT helper
Date: Sat, 13 Apr 2019 20:17:08 -0300 [thread overview]
Message-ID: <20190413231716.28711-1-fbl@redhat.com> (raw)
The request_module() is quite expensive and triggers the
usermode helper in userspace. Instead, load only if the
module is not present and keep module references to avoid
problems.
The first patch standardize the module alias which is already
there, but not in a formal way.
The second patch adds an API to point to the NAT helper.
The following patches will register each NAT helper using
the new API.
The last patch fixes openvswitch to use the new API to
load and reference the NAT helper and also report an error
if the operation fails.
Flavio Leitner (8):
netfilter: use macros to create module aliases.
netfilter: add API to manage NAT helpers.
netfilter: nf_nat: register amanda NAT helper.
netfilter: nf_nat: register ftp NAT helper.
netfilter: nf_nat: register irc NAT helper.
netfilter: nf_nat: register sip NAT helper.
netfilter: nf_nat: register tftp NAT helper.
openvswitch: load and reference the NAT helper.
include/net/netfilter/nf_conntrack_helper.h | 24 +++++
net/ipv4/netfilter/nf_nat_h323.c | 2 +-
net/ipv4/netfilter/nf_nat_pptp.c | 2 +-
net/netfilter/nf_conntrack_amanda.c | 8 +-
net/netfilter/nf_conntrack_ftp.c | 13 +--
net/netfilter/nf_conntrack_helper.c | 97 +++++++++++++++++++++
net/netfilter/nf_conntrack_irc.c | 6 +-
net/netfilter/nf_conntrack_sane.c | 12 +--
net/netfilter/nf_conntrack_sip.c | 28 +++---
net/netfilter/nf_conntrack_tftp.c | 18 ++--
net/netfilter/nf_nat_amanda.c | 9 +-
net/netfilter/nf_nat_ftp.c | 9 +-
net/netfilter/nf_nat_irc.c | 9 +-
net/netfilter/nf_nat_sip.c | 9 +-
net/netfilter/nf_nat_tftp.c | 9 +-
net/openvswitch/conntrack.c | 26 ++++--
16 files changed, 233 insertions(+), 48 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-13 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 23:17 Flavio Leitner [this message]
2019-04-13 23:17 ` [PATCH net-next v2 1/8] netfilter: use macros to create module aliases Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 2/8] netfilter: add API to manage NAT helpers Flavio Leitner
2019-04-15 5:48 ` Pablo Neira Ayuso
2019-04-15 14:04 ` Flavio Leitner
2019-04-15 5:50 ` Pablo Neira Ayuso
2019-04-15 14:05 ` Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 3/8] netfilter: nf_nat: register amanda NAT helper Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 4/8] netfilter: nf_nat: register ftp " Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 5/8] netfilter: nf_nat: register irc " Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 6/8] netfilter: nf_nat: register sip " Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 7/8] netfilter: nf_nat: register tftp " Flavio Leitner
2019-04-13 23:17 ` [PATCH net-next v2 8/8] openvswitch: load and reference the " Flavio Leitner
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=20190413231716.28711-1-fbl@redhat.com \
--to=fbl@redhat.com \
--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).