From: Tomas Szepe <szepe@pinerecords.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com, grof@dragon.cz,
davem@redhat.com
Subject: Re: possible bug in tcp_input.c
Date: Tue, 18 Nov 2003 14:58:05 +0100 [thread overview]
Message-ID: <20031118135805.GA9705@louise.pinerecords.com> (raw)
In-Reply-To: <p73ptgma58b.fsf@oldwotan.suse.de>
On Oct-24 2003, Fri, 19:57 +0200
Andi Kleen <ak@suse.de> wrote:
> > /* tcp_input.c, line 1138 */
> > static inline int tcp_head_timedout(struct sock *sk, struct tcp_opt *tp)
> > {
> > return tp->packets_out && tcp_skb_timedout(tp, skb_peek(&sk->write_queue));
> > }
>
> tp->packets_out > 0 implies that there is at least one packet in the write
> queue (it counts the number of unacked packets in flight, which are kept
> in the write queue). When that's not the case something else is wrong.
Yes, that's exactly what davem said. The corruption is happening somewhere
in netsched/imq code that's not even part of the official kernel tree (and
I'm told there's nobody to maintain the patch at present).
Thanks,
--
Tomas Szepe <szepe@pinerecords.com>
P.S. I can post the patchset we've been using on the crashing machines
in case someone's interested, it's reasonably short:
9101 Jul 6 11:48 bridge-nf-0.0.7-against-2.4.22pre3.diff.gz
4123 Jul 6 11:14 imq-2.4.22pre3-1.diff.gz
1883 Jul 6 12:01 imq-nf-20030625-2.4.22pre3.diff.gz
next prev parent reply other threads:[~2003-11-18 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031024162959.GB11154@louise.pinerecords.com.suse.lists.linux.kernel>
2003-10-24 17:57 ` possible bug in tcp_input.c Andi Kleen
2003-11-18 13:58 ` Tomas Szepe [this message]
2003-11-18 14:01 ` Andi Kleen
2003-10-24 16:29 Tomas Szepe
2003-10-25 2:30 ` David S. Miller
2003-10-25 9:12 ` Tomas Szepe
2003-10-26 6:55 ` Tomas Szepe
2003-10-27 6:33 ` David S. 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=20031118135805.GA9705@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=grof@dragon.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).