From: Herbert Xu <herbert@gondor.apana.org.au>
To: adobriyan@gmail.com (Alexey Dobriyan)
Cc: netdev@vger.kernel.org
Subject: Re: more info on ipsec-related invalid trusize
Date: Tue, 25 Nov 2008 18:52:16 +0800 [thread overview]
Message-ID: <E1L4vWi-0006zm-PX@gondolin.me.apana.org.au> (raw)
In-Reply-To: <20081125042752.GA4085@x200.localdomain>
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10996
> http://marc.info/?l=linux-netdev&m=122641698504902&w=2
>
> SKB BUG: Invalid truesize (344) len=134, sizeof(sk_buff)=216
>
> This correlates with ping6 the box to death with the following IPsec
> configuration and entering/leaving tcpdumping on the other end.
It's a known problem. When we expand packet headers in IPsec
we're not adjusting the truesize.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2008-11-25 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 4:28 more info on ipsec-related invalid trusize Alexey Dobriyan
2008-11-25 10:52 ` Herbert Xu [this message]
2008-11-26 5:50 ` David Miller
2008-11-26 5:57 ` 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=E1L4vWi-0006zm-PX@gondolin.me.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=adobriyan@gmail.com \
--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