From: Simon Horman <horms@verge.net.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>, Simon Horman <horms@verge.net.au>
Subject: [GIT PULL nf-next 0/1] Second Round of IPVS Updates for v4.7
Date: Fri, 6 May 2016 16:32:38 +0900 [thread overview]
Message-ID: <1462519959-22382-1-git-send-email-horms@verge.net.au> (raw)
Hi Pablo,
please consider these enhancements to the IPVS. They allow its
DoS mitigation strategy effective in conjunction with the SIP persistence
engine.
The following changes since commit cb39ad8b8ef224c544074962780bf763077d6141:
netfilter: nf_tables: allow set names up to 32 bytes (2016-05-05 16:39:51 +0200)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git tags/ipvs2-for-v4.7
for you to fetch changes up to 698e2a8dca98e4de32f3f630e6d9cd93753c52e1:
ipvs: make drop_entry protection effective for SIP-pe (2016-05-06 16:26:23 +0900)
----------------------------------------------------------------
Marco Angaroni (1):
ipvs: make drop_entry protection effective for SIP-pe
net/netfilter/ipvs/ip_vs_conn.c | 22 +++++++++++++++++++---
net/netfilter/ipvs/ip_vs_core.c | 8 +++++++-
2 files changed, 26 insertions(+), 4 deletions(-)
Marco Angaroni (1):
ipvs: make drop_entry protection effective for SIP-pe
net/netfilter/ipvs/ip_vs_conn.c | 22 +++++++++++++++++++---
net/netfilter/ipvs/ip_vs_core.c | 8 +++++++-
2 files changed, 26 insertions(+), 4 deletions(-)
--
2.7.0.rc3.207.g0ac5344
next reply other threads:[~2016-05-06 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 7:32 Simon Horman [this message]
2016-05-06 7:32 ` [PATCH nf-next 1/1] ipvs: make drop_entry protection effective for SIP-pe Simon Horman
2016-05-08 22:19 ` [GIT PULL nf-next 0/1] Second Round of IPVS Updates for v4.7 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=1462519959-22382-1-git-send-email-horms@verge.net.au \
--to=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wensong@linux-vs.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).