mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lazy <lazy404@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: SKB BUG: Invalid truesize (412) len=28, ipsec related ?
Date: Thu, 7 Aug 2008 16:48:37 +0200	[thread overview]
Message-ID: <efeafa350808070748t652a77cm9bf28aad851aa791@mail.gmail.com> (raw)

vanilla 2.6.25.13, working as a router, 4 interfaces about 100MBit/s traffic
using e1000 and tg3 ethernet drivers

it's a production machine so I basicly can't touch it now, I think
it's triggerd by ipsec tunnel because
before rolling this machine on production it was stress tested
(without the tunnel) to tune the firewall,
and there ware no BUG()'s triggerd.

Aug  7 07:16:49 cisco-ng kernel: SKB BUG: Invalid truesize (412)
len=286, sizeof(sk_buff)=156
Aug  7 07:16:51 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=142, sizeof(sk_buff)=156
Aug  7 07:16:51 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=142, sizeof(sk_buff)=156
Aug  7 07:16:54 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=134, sizeof(sk_buff)=156
Aug  7 07:16:55 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=134, sizeof(sk_buff)=156
Aug  7 07:16:59 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=142, sizeof(sk_buff)=156
Aug  7 07:16:59 cisco-ng kernel: SKB BUG: Invalid truesize (284)
len=142, sizeof(sk_buff)=156

tunnel is created by setkey
add 10.0.5.2 10.0.5.1 esp 0xxxx -m tunnel -E 3des-cbc ...

Tomorrow i will try to trigger it in a test environment, any pointers
how to get more info out of it?
I found this http://lists.openwall.net/netdev/2008/05/06/61 will it be ok ?

-- 
Michal Grzedzicki

             reply	other threads:[~2008-08-07 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 14:48 Lazy [this message]
2008-09-16 12:40 ` Lazy

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=efeafa350808070748t652a77cm9bf28aad851aa791@mail.gmail.com \
    --to=lazy404@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®