All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wei <lw@cn.fujitsu.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Question with commit 299b0767(ipv6: Fix IPsec slowpath fragmentation problem)
Date: Mon, 13 Feb 2012 16:10:39 +0800	[thread overview]
Message-ID: <4F38C57F.5000706@cn.fujitsu.com> (raw)

Hi, Steffen!

I found some problem while doing networking tests with IPSec that
the first fragment doesn't use the max MTU to fill payload, but with
20 bytes smaller. When I reverted your commit 299b0767(ipv6: Fix 
IPsec slowpath fragmentation problem), things goes well.

Would you so kindly to point me out what the commit did, because I
think the original implementation had taken IPSec header and tailer
into account.

Thanks!

             reply	other threads:[~2012-02-13  8:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  8:10 Li Wei [this message]
2012-02-14 11:04 ` Question with commit 299b0767(ipv6: Fix IPsec slowpath fragmentation problem) Steffen Klassert
2012-02-15  7:00   ` Li Wei
2012-02-15 10:40     ` Steffen Klassert
2012-05-14  3:21       ` [PATCH] ipv6: fix incorrect ipsec transport mode fragment Gao feng
2012-05-14 13:05         ` Steffen Klassert
2012-05-14 22:41           ` David Miller
2012-05-17  7:42             ` Gao feng
2012-05-17  8:48               ` David Miller
2012-05-15  3:44           ` Gao feng
2012-05-15 11:48             ` Steffen Klassert
2012-05-16  2:59               ` Gao feng
2012-05-26  9:00           ` Gao feng
2012-05-26 11:29             ` Gao feng
2012-05-26 11:30         ` [PATCH v2] ipv6: fix incorrect ipsec fragment Gao feng
2012-05-27  5:12           ` 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=4F38C57F.5000706@cn.fujitsu.com \
    --to=lw@cn.fujitsu.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.