netdev - Re: Telnet closing delay

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Apr 2008 14:42:07 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Beschorner Daniel <Daniel.Beschorner@...ton.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Telnet closing delay

Hi.

On Thu, Apr 03, 2008 at 11:32:14AM +0200, Beschorner Daniel (Daniel.Beschorner@...ton.com) wrote:
> >> 0.000095 select(4, [0 3], [], [0], NULL) = 1 (in [3])
> >> 0.001779 read(3, 0x8059de0, 8192)  = -1 EIO (Input/output error)
> 
> > Hmm, does not it supposed to stop doing such things on the closed
> > socket and not enter 10000 select/read loop?
> > Server behaves incorrectly in this scenario, why and how it can be
> fixed
> > is another questions better asked the author.
> 
> It must have been indeed triggered by a kernel change or bug, with
> current 2.6.24.4 all works fine again.

I really do not remember what was one year ago, but having a long loop
checking closed socket status is wrong. In recent kernels returned error
could be changed to something like -EINVAL, which is correctly handled
by application, it is impossible to say without caling mind readers, but
they are on vacations right now...

It can be some obscure kernel bug which was fixed or hidden, but with
above description it is hardly possible to tell what is going on.

-- 
	Evgeniy Polyakov
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html