Re: commit 64ff3b938ec6782e6585a83d5459b98b0c3f6eb8 breaks rlogin

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Mon, 9 Feb 2009 16:58:48 +1100

On Fri, Feb 06, 2009 at 07:35:50PM +0800, Jeff Chua wrote:

quoted

quoted

Did you change the kernel on the other side during these tests?

No. Was hoping that the traces would show where it hang for the good
and bad trace.

Then the problem isn't my patch at all.  My patch only affects
the side sending the urgent data, according to your straces, rlogin
is only receiving urgent data, not sending it.  So the patch cannot
have an affect.

Hmmm... let's figure out exactly what's going on here.

I would expect to see the URG packets from rlogin not rlogind, from
things like hitting Ctrl-C etc.

On the other hand, I can't imagine what the server, rlogind, would be
sending URGs out for.

So I would say that it is more likely to be rlogin sending the
URG packets.