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] IPVS fix for v3.10
Date: Wed, 19 Jun 2013 10:56:01 +0900 [thread overview]
Message-ID: <1371606963-30548-1-git-send-email-horms@verge.net.au> (raw)
Hi Pablo,
I realise this is rather late in the cycle, so please feel free
to push back on this. We can add it to v3.11 and then -stable.
This fix appears to resolve a long-standing problem that has
existed since SCTP support was added to IPVS in v2.6.32.
I believe it is relevant to -stable all the way back until then.
The following changes since commit b396966c4688522863572927cb30aa874b3ec504:
netfilter: xt_TCPMSS: Fix missing fragmentation handling (2013-06-12 11:06:19 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git tags/ipvs-fixes-for-v3.10
for you to fetch changes up to 06f3d7f973ec04290d86b7dd91b48d38d90433dc:
ipvs: SCTP ports should be writable in ICMP packets (2013-06-19 09:53:52 +0900)
----------------------------------------------------------------
IPVS fix for v3.10
Correct long standing bug in treatment of SCTP
when it it is embeded in ICMP from a client.
----------------------------------------------------------------
Julian Anastasov (1):
ipvs: SCTP ports should be writable in ICMP packets
net/netfilter/ipvs/ip_vs_core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
1.8.2.1
next reply other threads:[~2013-06-19 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 1:56 Simon Horman [this message]
2013-06-19 1:56 ` [PATCH nf] ipvs: SCTP ports should be writable in ICMP packets Simon Horman
2013-06-20 9:47 ` [GIT PULL nf] IPVS fix for v3.10 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=1371606963-30548-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).