From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.hengli.com.au, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] xfrm6: Don't call icmpv6_send on local error
Date: Tue, 18 Oct 2011 23:53:26 -0400 (EDT) [thread overview]
Message-ID: <20111018.235326.728003889061782561.davem@davemloft.net> (raw)
In-Reply-To: <20111011114430.GJ1830@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Tue, 11 Oct 2011 13:44:30 +0200
> Calling icmpv6_send() on a local message size error leads to
> an incorrect update of the path mtu. So use xfrm6_local_rxpmtu()
> to notify about the pmtu if the IPV6_DONTFRAG socket option is
> set on an udp or raw socket, according RFC 3542 and use
> ipv6_local_error() otherwise.
>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Applied.
prev parent reply other threads:[~2011-10-19 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 11:42 [PATCH net-next 0/2] ipv6: IPsec pmtu/fragmentation fixes Steffen Klassert
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 [this message]
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=20111018.235326.728003889061782561.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).