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] Second round of IPVS fixes for v3.17
Date: Thu, 28 Aug 2014 11:04:27 +0900 [thread overview]
Message-ID: <1409191468-28013-1-git-send-email-horms@verge.net.au> (raw)
Hi Pablo,
please consider this fix IPVS fix for v3.17.
This pull request is based on the first round of fixes for IPVS for v3.17,
tagged as ipvs-fixes2-for-v3.17, which I sent yesterday.
This fix resolves a problem with conflicting hooks whereby DNAT support for
the local server would drop outgoing IPv4 packets if the kernel was
compiled CONFIG_IP_VS_IPV6=y.
This problem dates back to v3.6.37 when the feature in question was added.
I would like this fix considered for -stable.
The following changes since commit ea1d5d7755a3e556de78cc757d1895d5c7180548:
ipvs: properly declare tunnel encapsulation (2014-08-27 14:31:56 +0900)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git tags/ipvs-fixes2-for-v3.17
for you to fetch changes up to eb90b0c734ad793d5f5bf230a9e9a4dcc48df8aa:
ipvs: fix ipv6 hook registration for local replies (2014-08-28 10:52:37 +0900)
----------------------------------------------------------------
Julian Anastasov (1):
ipvs: fix ipv6 hook registration for local replies
net/netfilter/ipvs/ip_vs_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2014-08-28 2:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 2:04 Simon Horman [this message]
2014-08-28 2:04 ` [PATCH nf] ipvs: fix ipv6 hook registration for local replies Simon Horman
2014-08-30 11:08 ` [GIT PULL nf] Second round of IPVS fixes for v3.17 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=1409191468-28013-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).