From: "Markus Werner" <markiwer@googlemail.com>
To: "Beschorner Daniel" <Daniel.Beschorner@facton.com>
Cc: "Ben Hutchings" <bhutchings@solarflare.com>, netdev@vger.kernel.org
Subject: Re: Invalid truesize messages since 2.6.25
Date: Tue, 22 Jul 2008 19:20:48 +0200 [thread overview]
Message-ID: <8a75de9b0807221020s6831bebahafa4de57e93d3098@mail.gmail.com> (raw)
In-Reply-To: <3C59DB883F7B0B4D8096010D45ACCD13C73B02@exch.facton.local>
2008/7/22 Beschorner Daniel <Daniel.Beschorner@facton.com>:
>>> Since 2.6.25 we rarely see these messages:
>>>
>>> SKB BUG: Invalid truesize (408) len=198, sizeof(sk_buff)=216
Same problem here.
>>> Yesterday I saw it the first time after a runtime of one week with
>>> 2.6.26.
>>> The box is web server / IPSEC gateway.
>>> Obviously nothing seems to be affected by the message but <= 2.6.24
> no
>>> messages appeared.
>
>> Invalid truesize can be caused by bugs in many different places. So
> it
>> might be helpful to say which driver(s) and any unusual network
> protocol
>> or filter you are using.
>
> Network driver: tg3
> IPSEC: esp tunnels, ipcomp, 3des/aes
> I use this config so far on other servers too without this message.
Kernel: 2.6.26
Tested drivers: pcnet32, e1000, vmxnet
> The unusal part special to this server may be:
> Bandwidth management via htb & sfq, CONFIG_IP_MULTIPLE_TABLES for source
> IP routing
Both are used here too, but no IPSec.
This box is a router to the internet and an openvpn gateway. The
problem is not reliably reproducible, but it seems to happen when the
box is routing udp traffic, for example heavy openvpn usage or video
streaming via udp.
Markus
next prev parent reply other threads:[~2008-07-22 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 8:54 Invalid truesize messages since 2.6.25 Beschorner Daniel
2008-07-22 11:43 ` Ben Hutchings
2008-07-22 12:06 ` Beschorner Daniel
2008-07-22 17:20 ` Markus Werner [this message]
2008-07-23 7:55 ` Marco Berizzi
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 17:53 Beschorner Daniel
2008-09-26 21:53 ` Ben Hutchings
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=8a75de9b0807221020s6831bebahafa4de57e93d3098@mail.gmail.com \
--to=markiwer@googlemail.com \
--cc=Daniel.Beschorner@facton.com \
--cc=bhutchings@solarflare.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;
as well as URLs for NNTP newsgroup(s).