From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Krzysztof Oledzki <ole@ans.pl>,
Marco Berizzi <pupilla@hotmail.com>,
netdev@vger.kernel.org
Subject: Re: WARNING: at net/core/skbuff.c:154 with tcpdump and ipsec
Date: Fri, 13 Feb 2009 13:56:01 -0500 [thread overview]
Message-ID: <4995C241.1030507@hp.com> (raw)
In-Reply-To: <20090213121424.GA8717@ff.dom.local>
Jarek Poplawski wrote:
> On 11-02-2009 16:55, Krzysztof Oledzki wrote:
>> On Wed, 11 Feb 2009, Marco Berizzi wrote:
>>
>>> Hi Folks,
>>>
>>> I'm getting this error on 2.6.28.4 when I run tcpdump on
>>> the interface where ipsec packets are enc/decrypted.
>>>
>>> TIA
>>>
>>>> Feb 11 10:53:55 Pleiadi kernel: ------------[ cut here ]------------
>>>> Feb 11 10:53:55 Pleiadi kernel: WARNING: at net/core/skbuff.c:154 skb_truesize_bug+0x2e/0x33()
>>>> Feb 11 10:53:55 Pleiadi kernel: SKB BUG: Invalid truesize (268) len=134, sizeof(sk_buff)=172
>> <CUT>
>>
>> This annoying problem is quite old (appeared in 2.6.25) and already known:
>> http://bugzilla.kernel.org/show_bug.cgi?id=10996
>>
>> Sadly, no one is interested in fixing it. :(
>
> Here is a debugging patch doing these checks a bit earlier, so maybe
> we get something new and interesting. ;)
>
> Thanks,
> Jarek P.
> ---
>
I did notice that pskb_expand_head() doesn't change the skb->truesize even
though it could grow the skb. I saw this problem with tcpdump while
experimenting with some SCTP code.
This is not to say that it is the problem in this case, but it's one of
them that I've seen.
-vlad
next prev parent reply other threads:[~2009-02-13 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 15:26 WARNING: at net/core/skbuff.c:154 with tcpdump and ipsec Marco Berizzi
2009-02-11 15:55 ` Krzysztof Oledzki
2009-02-11 18:25 ` Jarek Poplawski
2009-02-13 12:14 ` Jarek Poplawski
2009-02-13 18:56 ` Vlad Yasevich [this message]
2009-02-13 19:24 ` Jarek Poplawski
2009-02-13 19:42 ` Vlad Yasevich
2009-02-13 20:00 ` Jarek Poplawski
2009-02-14 2:24 ` David Miller
2009-02-18 9:13 ` 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=4995C241.1030507@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
--cc=pupilla@hotmail.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 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).