From: Rob Herring <robherring2@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: panics in tcp_ack
Date: Sun, 02 Jun 2013 22:41:02 -0500 [thread overview]
Message-ID: <51AC104E.90100@gmail.com> (raw)
In-Reply-To: <1370230370.24311.121.camel@edumazet-glaptop>
On 06/02/2013 10:32 PM, Eric Dumazet wrote:
> On Sun, 2013-06-02 at 22:18 -0500, Rob Herring wrote:
>
>> Ah, missed that there are 2 versions of skb_transport_header. So on
>> 32-bit it is skb->transport_header.
>>
>> Here's the ARM disassembly:
>>
>> c040796c <tcp_rcv_established>:
>> c040796c: e92d45f0 push {r4, r5, r6, r7, r8, sl, lr}
>> c0407970: e1a06002 mov r6, r2
>> c0407974: e5d023e4 ldrb r2, [r0, #996] ; 0x3e4
>> c0407978: e1a05001 mov r5, r1
>> c040797c: e5901344 ldr r1, [r0, #836] ; 0x344
>> c0407980: e24dd014 sub sp, sp, #20
>> c0407984: e7c0201f bfc r2, #0, #1
>> c0407988: e5c023e4 strb r2, [r0, #996] ; 0x3e4
>> panic>c040798c: e596200c ldr r2, [r6, #12]
>>
>> r6 is NULL. r6 came from r2 which is the 3rd function argument.
>>
>> The 3rd arg is tcp_hdr(skb) which is skb->transport_header.
>>
>> Rob
>
> Interesting. transport header should be set in IP stack before TCP.
>
> What is the driver delivering this packet ?
Calxeda xgmac
> Do you have commit fda55eca5a33f33ffcd4192c6b2d75179714a52c
> ("net: introduce skb_transport_header_was_set()")
No.
Rob
next prev parent reply other threads:[~2013-06-03 4:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 0:16 panics in tcp_ack Rob Herring
2013-06-03 0:24 ` Eric Dumazet
2013-06-03 0:26 ` Eric Dumazet
2013-06-03 0:36 ` Eric Dumazet
2013-06-03 2:23 ` Rob Herring
2013-06-03 3:03 ` Eric Dumazet
2013-06-03 3:18 ` Rob Herring
2013-06-03 3:32 ` Eric Dumazet
2013-06-03 3:41 ` Rob Herring [this message]
2013-06-03 13:05 ` Rob Herring
2013-06-03 13:25 ` Eric Dumazet
2013-06-03 15:51 ` Rob Herring
2013-06-03 15:58 ` Eric Dumazet
2013-06-14 19:12 ` Rob Herring
2013-06-14 20:52 ` Eric Dumazet
2013-06-06 17:21 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2013-06-03 0:13 Rob Herring
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=51AC104E.90100@gmail.com \
--to=robherring2@gmail.com \
--cc=eric.dumazet@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;
as well as URLs for NNTP newsgroup(s).