From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] ipv6: IPsec pmtu/fragmentation fixes
Date: Tue, 11 Oct 2011 13:42:51 +0200 [thread overview]
Message-ID: <20111011114251.GH1830@secunet.com> (raw)
This patchset fixes two issues for IPsec on ipv6. These issues
are arround, basically forever.
The patchset is based on current net-next/master.
1) Fix for a IPv6 IPsec slowpath fragmentation problem.
Already fixed for IPv4 with
git commit 353e5c9 (ipv4: Fix IPsec slowpath fragmentation problem).
2) Fix an incorrect update of the path mtu on IPv6 IPsec.
Already fixed for IPv4 with
git commit b00897b (xfrm4: Don't call icmp_send on local error).
next reply other threads:[~2011-10-11 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 11:42 Steffen Klassert [this message]
2011-10-11 11:43 ` [PATCH 1/2] ipv6: Fix IPsec slowpath fragmentation problem Steffen Klassert
2011-10-19 3:53 ` David Miller
2011-10-11 11:44 ` [PATCH 2/2] xfrm6: Don't call icmpv6_send on local error Steffen Klassert
2011-10-19 3:53 ` 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=20111011114251.GH1830@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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).