[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090208.220357.261414983.davem@davemloft.net>
Date: Sun, 08 Feb 2009 22:03:57 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: herbert@...dor.apana.org.au
Cc: jeff.chua.linux@...il.com, rjw@...k.pl,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: commit 64ff3b938ec6782e6585a83d5459b98b0c3f6eb8 breaks rlogin
From: Herbert Xu <herbert@...dor.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:
> >
> > > 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists