mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: herbert@gondor.apana.org.au, David Miller <davem@davemloft.net>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: commit 64ff3b938ec6782e6585a83d5459b98b0c3f6eb8 breaks rlogin
Date: Thu, 5 Feb 2009 22:41:52 +0800	[thread overview]
Message-ID: <b6a2187b0902050641h7943816ds26275a320e724440@mail.gmail.com> (raw)

The following commit breaks "rlogin". Symptom is the terminal just
hangs before login to the remote machine. No error, just the cursor
never come back. "~." or type "exit" will exit from remote session.
Only happens "sometimes". Happens more often if you try many times.

I've reverted the commit, and rlogin works now.

Thanks,
Jeff.



commit 64ff3b938ec6782e6585a83d5459b98b0c3f6eb8
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date:   Thu Dec 25 17:12:58 2008 -0800

    tcp: Always set urgent pointer if it's beyond snd_nxt

    Our TCP stack does not set the urgent flag if the urgent pointer
    does not fit in 16 bits, i.e., if it is more than 64K from the
    sequence number of a packet.

    This behaviour is different from the BSDs, and clearly contradicts
    the purpose of urgent mode, which is to send the notification
    (though not necessarily the associated data) as soon as possible.
    Our current behaviour may in fact delay the urgent notification
    indefinitely if the receiver window does not open up.

    Simply matching BSD however may break legacy applications which
    incorrectly rely on the out-of-band delivery of urgent data, and
    conversely the in-band delivery of non-urgent data.

             reply	other threads:[~2009-02-05 14:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 14:41 Jeff Chua [this message]
2009-02-05 23:29 ` David Miller
2009-02-05 23:32   ` Linus Torvalds
2009-02-05 23:38     ` David Miller
2009-02-05 23:52     ` Herbert Xu
2009-02-06  3:10 ` Herbert Xu
2009-02-06  5:39   ` Jeff Chua
2009-02-06  5:45     ` Herbert Xu
2009-02-06 11:35       ` Jeff Chua
2009-02-09  5:58         ` Herbert Xu
2009-02-09  6:03           ` David Miller
2009-02-09  6:11             ` Herbert Xu
2009-02-09  7:13               ` Ilpo Järvinen
2009-02-09  7:28                 ` Herbert Xu
2009-02-09  7:33                   ` Herbert Xu
2009-02-09 13:28                   ` Ilpo Järvinen
2009-02-21 13:24                     ` Herbert Xu
2009-02-21 18:54                       ` Ilpo Järvinen
2009-02-22  7:53                         ` David Miller
2009-02-24  6:40                           ` Jeff Chua
2009-02-24  6:44                             ` Herbert Xu
2009-02-24  6:46                             ` David Miller
2009-02-24  8:01                               ` Jeff Chua
2009-02-09 14:10                 ` Jeff Chua
2009-02-09 15:44           ` Linus Torvalds
2009-02-09 21:17             ` Herbert Xu

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=b6a2187b0902050641h7943816ds26275a320e724440@mail.gmail.com \
    --to=jeff.chua.linux@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®