From: Andi Kleen <ak@suse.de>
To: Tomas Szepe <szepe@pinerecords.com>
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: 24 Oct 2003 19:57:24 +0200 [thread overview]
Message-ID: <p73ptgma58b.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20031024162959.GB11154@louise.pinerecords.com.suse.lists.linux.kernel>
Tomas Szepe <szepe@pinerecords.com> writes:
> /* 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.
-Andi
next parent reply other threads:[~2003-10-24 17:57 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 ` Andi Kleen [this message]
2003-11-18 13:58 ` possible bug in tcp_input.c Tomas Szepe
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=p73ptgma58b.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=grof@dragon.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=szepe@pinerecords.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).