netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: [TCP]: Fix TCP header misalignment
Date: Sun, 18 Nov 2007 13:36:02 -0800 (PST)	[thread overview]
Message-ID: <20071118.133602.193701128.davem@davemloft.net> (raw)
In-Reply-To: <20071118121530.GA27963@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Sun, 18 Nov 2007 20:15:30 +0800

> [TCP]: Fix TCP header misalignment
> 
> Indeed my previous change to alloc_pskb has made it possible
> for the TCP header to be misaligned iff the MTU is not a multiple
> of 4 (and less than a page).  So I suspect the optimised IPsec
> MTU calculation is giving you just such an MTU :)
> 
> This patch fixes it by changing alloc_pskb to make sure that
> the size is at least 32-bit aligned.  This does not cause the
> problem fixed by the previous patch because max_header is always
> 32-bit aligned which means that in the SG/NOTSO case this will
> be a no-op.
> 
> I thought about putting this in the callers but all the current
> callers are from TCP.  If and when we get a non-TCP caller we
> can always create a TCP wrapper for this function and move the
> alignment over there.
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

I'm getting this without IPSEC FWIW.  I believe it occurs when I talk
to sites with sub-1500 MTUs.

I'll test your patch and let you know how it goes, thanks.

  reply	other threads:[~2007-11-18 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-18 12:15 [TCP]: Fix TCP header misalignment Herbert Xu
2007-11-18 21:36 ` David Miller [this message]
2007-11-19  1:28   ` Herbert Xu

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=20071118.133602.193701128.davem@davemloft.net \
    --to=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).