From: Andrew Morton <akpm@linux-foundation.org>
To: "Ilpo =?ISO-8859-1?B?SuRydmluZW4i?=
<ilpo.jarvinen@helsinki.fi>"@linux-foundation.org
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: tcp crash in net-2.6 tree
Date: Fri, 30 Mar 2007 09:18:25 -0700 [thread overview]
Message-ID: <20070330091825.c0b57081.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703301618510.23854@kivilampi-30.cs.helsinki.fi>
On Fri, 30 Mar 2007 17:33:28 +0300 (EEST) "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> On Thu, 29 Mar 2007, Andrew Morton wrote:
>
> > Full -mm lineup. The x86_64 box was acting as a distcc server at the time.
> >
> > Nothing hit the logs, I'm afraid. But almost all the info is in
> > http://userweb.kernel.org/~akpm/s5000494.jpg
> >
> > <pokes around in gdb a bit>
> >
> > It died in tcp_update_scoreboard_fack() here:
> >
> > if ((!IsFack(tp) || !tcp_skb_timedout(sk, skb)) &&
> > after(TCP_SKB_CB(skb)->seq, tp->high_seq)) {
> > /* RFC: should we have find_below? */
> > skb = tcp_write_queue_find(sk, tp->high_seq);
> > not_marked_skb = skb;
> > skb = tcp_write_queue_prev(sk, skb);
> > /* Timedout top is again uncertain? */
> > if (tcp_skb_timedout(sk, skb))
> > timedout_continue = 1;
> > }
> >
> >
> > (gdb) l *0xffffffff8048ded8
> > 0xffffffff8048ded8 is in tcp_update_scoreboard_fack (include/net/tcp.h:1197).
> > 1192 return skb->next;
> > 1193 }
> > 1194
> > 1195 static inline struct sk_buff *tcp_write_queue_prev(struct sock *sk, struct sk_buff *skb)
> > 1196 {
> > 1197 return skb->prev;
> > 1198 }
> > 1199
> > 1200 #define tcp_for_write_queue(skb, sk) \
> >
> > (gdb) x/10i 0xffffffff8048ded8
> > 0xffffffff8048ded8 <tcp_update_scoreboard_fack+528>: mov 0x8(%rdx),%r12
> >
> > So if that "CR2: 0000000000000008" is the access address then it appears that
> > `skb' is NULL. tcp_write_queue_find() didn't find nuthin.
>
> If there is nothing at high_seq (application hasn't given any data to/past
> that point), the search fails to find any skb and returns NULL... But I
> have no idea how this can happen? As TCP does after(skb->seq,
> tp->high_seq) (even in the quoted code block) guaranteeing that something
> is there after the high_seq for TCP to step temporarily on... So at least
> one skb should have it's end_seq after tp->high_seq (actually there
> should be at least two valid skbs after tp->high_seq since the used
> sequence number space does not have holes), which should be enough to get
> an existing skb from write_queue_find?!
>
> I also checked all call paths to tcp_update_scoreboard_fack to make sure
> that snd_una hasn't gone past high_seq and found nothing suspicious (and
> that wouldn't return NULL anyway I think)...
Well, could I suggest that you prepare a patch which adds lots of debugging
checks in that area? I can apply it and will rerun the same workload.
next prev parent reply other threads:[~2007-03-30 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 6:09 tcp crash in net-2.6 tree Andrew Morton
2007-03-30 14:33 ` Ilpo Järvinen
2007-03-30 16:18 ` Andrew Morton [this message]
2007-03-30 21:43 ` David Miller
2007-03-30 22:06 ` Andrew Morton
2007-03-30 22:12 ` David Miller
2007-03-30 22:10 ` Thomas Graf
2007-03-30 22:15 ` David Miller
2007-03-31 10:19 ` ijjarvin
2007-04-02 8:38 ` Ilpo Järvinen
2007-04-02 9:02 ` David Miller
2007-04-02 21:06 ` Thomas Graf
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=20070330091825.c0b57081.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc="Ilpo =?ISO-8859-1?B?SuRydmluZW4i?= <ilpo.jarvinen@helsinki.fi>"@linux-foundation.org \
--cc=davem@davemloft.net \
--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).