From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, pupilla@hotmail.com
Subject: Re: [XFRM]: Fix MTU calculation for non-ESP SAs
Date: Tue, 19 Jun 2007 14:02:30 +0200 [thread overview]
Message-ID: <4677C5D6.20005@trash.net> (raw)
In-Reply-To: <20070618.223101.39174669.davem@davemloft.net>
David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Mon, 18 Jun 2007 18:09:11 +0200
>
>
>>[XFRM]: Fix MTU calculation for non-ESP SAs
>>
>>My IPsec MTU optimization patch introduced a regression in MTU calculation
>>for non-ESP SAs, the SA's header_len needs to be subtracted from the MTU if
>>the transform doesn't provide a ->get_mtu() function.
>>
>
> Patch applied, thanks a lot Patrick.
>
> We only need this for 2.6.22 right?
Yes, the patch that broke this went into the first 2.6.22-rc.
prev parent reply other threads:[~2007-06-19 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 16:09 [XFRM]: Fix MTU calculation for non-ESP SAs Patrick McHardy
2007-06-19 5:31 ` David Miller
2007-06-19 12:02 ` Patrick McHardy [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=4677C5D6.20005@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pupilla@hotmail.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).