All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: kuznet@ms2.inr.ac.ru
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [TEST FIX] Re: SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x,
Date: Mon, 27 Jan 2003 22:22:24 -0500	[thread overview]
Message-ID: <20030128032224.GD18298@redhat.com> (raw)
In-Reply-To: <200301280257.FAA27287@sex.inr.ac.ru>

On Tue, Jan 28, 2003 at 05:57:55AM +0300, kuznet@ms2.inr.ac.ru wrote:
>>Alexey, this piece of code was buggy first time it was coded, and it
>>may still have some holes.  :-)))
>
>To my shame, I cannot say "no".  It was written sort of too fast.  :-)
>
>Did the reporters see packets with wrong checksum on wire or wrong tcp
>headers or something like that?

My knowledge of TCP/IP is extremely minimal but the sequence number looked
weird when the stall occurred.  It looked like the sequence numbers you get
with the -S option to tcpdump.  All of the other packets had small sequence
numbers and what I assume was the bad packet had a large one.

I'm sorry if this is gibberish and makes no sense.  I don't know how to tell
if the checksum was wrong or not.

cgf

  reply	other threads:[~2003-01-28  3:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 18:43 SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, through Cisco PIX David C Niemi
2003-01-24 20:29 ` David S. Miller
2003-01-24 20:46 ` lost
2003-01-24 21:15   ` Christopher Faylor
2003-01-25  2:00     ` SSH Hangs in 2.5.59 and 2.5.55 (TCP_NODELAY?) Christopher Faylor
2003-01-27 14:27 ` SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, through Cisco PIX David C Niemi
2003-01-27 18:06   ` David S. Miller
2003-01-27 18:11   ` David S. Miller
2003-01-27 18:28     ` Anders Gustafsson
2003-01-27 22:36       ` [TEST FIX] " David S. Miller
2003-01-28  2:25         ` lost
2003-01-28  2:57         ` [TEST FIX] Re: SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, kuznet
2003-01-28  3:22           ` Christopher Faylor [this message]
2003-01-28  3:39         ` [TEST FIX] Re: SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, through Cisco PIX Christopher Faylor
2003-01-28  3:55           ` kuznet
2003-01-28  7:08             ` dada1
2003-01-28 12:36               ` Sebastian Benoit
2003-01-28 14:09                 ` kuznet
2003-01-28 18:35                   ` David S. Miller
2003-01-28 19:16                     ` Sebastian Benoit
2003-01-28 20:34                       ` David S. Miller
2003-01-28 21:59                         ` Christopher Faylor
2003-01-28 22:12                         ` Sebastian Benoit
2003-01-28 23:21                           ` David S. Miller
2003-01-29  0:02                             ` [TEST FIX] Re: SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, kuznet
2003-01-29  0:09                             ` kuznet
2003-01-29  0:46                               ` Sebastian Benoit
2003-01-29  4:12                                 ` Christopher Faylor
2003-01-29  6:52                               ` David S. Miller
2003-01-28 23:56                         ` kuznet
2003-01-29  0:08                           ` David S. Miller
2003-01-29  3:14                             ` kuznet
2003-01-29  7:32                               ` David S. Miller
2003-01-29 14:12                             ` David C Niemi
2003-01-29 14:24                               ` kuznet
2003-01-29 15:11                                 ` dada1
2003-02-02 15:40                               ` Bill Davidsen
2003-01-27 21:27 ` SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, through Cisco PIX Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-02-03 14:23 [TEST FIX] Re: SSH Hangs in 2.5.59 and 2.5.55 but not 2.4.x, Franz Sirl
2003-02-03 17:11 ` J Sloan
2003-02-03 18:22   ` Jeff Garzik
2003-02-03 21:04 ` Bill Davidsen
     [not found] <Pine.LNX.3.96.1030203155651.28323A-100000@dstl.gov.uk>
2003-02-04  9:58 ` Tony Gale
2003-02-04 14:12   ` David Ford
2003-02-04 14:40   ` Bill Davidsen
2003-02-04 19:54 jjs

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=20030128032224.GD18298@redhat.com \
    --to=cgf@redhat.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.