From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [PATCH 0/6] Netfilter/IPVS fixes for net
Date: Tue, 1 Oct 2013 11:08:25 +0200 [thread overview]
Message-ID: <1380618511-6109-1-git-send-email-pablo@netfilter.org> (raw)
Hi David,
The following patchset contains Netfilter/IPVS fixes for your net
tree, they are:
* Fix BUG_ON splat due to malformed TCP packets seen by synproxy, from
Patrick McHardy.
* Fix possible weight overflow in lblc and lblcr schedulers due to
32-bits arithmetics, from Simon Kirby.
* Fix possible memory access race in the lblc and lblcr schedulers,
introduced when it was converted to use RCU, two patches from
Julian Anastasov.
* Fix hard dependency on CPU 0 when reading per-cpu stats in the
rate estimator, from Julian Anastasov.
* Fix race that may lead to object use after release, when invoking
ipvsadm -C && ipvsadm -R, introduced when adding RCU, from Julian
Anastasov.
You can pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git master
Thanks!
----------------------------------------------------------------
The following changes since commit 61c5923a2f2d8ab98a1e3c76f17e0f4a871ec75b:
Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf (2013-09-17 20:22:53 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git master
for you to fetch changes up to f4a87e7bd2eaef26a3ca25437ce8b807de2966ad:
netfilter: synproxy: fix BUG_ON triggered by corrupt TCP packets (2013-09-30 12:44:38 +0200)
----------------------------------------------------------------
Julian Anastasov (4):
ipvs: make the service replacement more robust
ipvs: do not use dest after ip_vs_dest_put in LBLC
ipvs: do not use dest after ip_vs_dest_put in LBLCR
ipvs: stats should not depend on CPU 0
Patrick McHardy (1):
netfilter: synproxy: fix BUG_ON triggered by corrupt TCP packets
Simon Kirby (1):
ipvs: fix overflow on dest weight multiply
include/net/ip_vs.h | 9 +--
include/net/netfilter/nf_conntrack_synproxy.h | 2 +-
net/ipv4/netfilter/ipt_SYNPROXY.c | 10 ++-
net/ipv6/netfilter/ip6t_SYNPROXY.c | 10 ++-
net/netfilter/ipvs/ip_vs_core.c | 12 +++-
net/netfilter/ipvs/ip_vs_ctl.c | 86 ++++++++++---------------
net/netfilter/ipvs/ip_vs_est.c | 4 +-
net/netfilter/ipvs/ip_vs_lblc.c | 72 ++++++++++-----------
net/netfilter/ipvs/ip_vs_lblcr.c | 62 ++++++++----------
net/netfilter/ipvs/ip_vs_nq.c | 8 +--
net/netfilter/ipvs/ip_vs_sed.c | 8 +--
net/netfilter/ipvs/ip_vs_wlc.c | 6 +-
net/netfilter/nf_synproxy_core.c | 12 ++--
13 files changed, 143 insertions(+), 158 deletions(-)
next reply other threads:[~2013-10-01 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 9:08 Pablo Neira Ayuso [this message]
2013-10-01 16:39 ` [PATCH 0/6] Netfilter/IPVS fixes for net David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-10-31 12:18 [PATCH 0/6] netfilter/ipvs " Pablo Neira Ayuso
2014-10-31 16:30 ` David Miller
2015-01-10 18:50 Pablo Neira Ayuso
2015-01-12 5:15 ` David Miller
2016-07-12 16:10 [PATCH 0/6] Netfilter/IPVS " Pablo Neira Ayuso
2016-07-12 17:22 ` 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=1380618511-6109-1-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).