linux-kernel - possible causes for EADDRINUSE in client code

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>] [day] [month] [year] [list]

Message-ID: <jbl0pd$g9q$1@dough.gmane.org>
Date:	Tue, 6 Dec 2011 12:11:26 +0000 (UTC)
From:	Steven Seagull <steven7779@....net>
To:	linux-kernel@...r.kernel.org
Subject: possible causes for EADDRINUSE in client code

Hi!

I'm running a 2.6.26 kernel where I have to create short-lived TCP
connections with a high frequency. In order to do this, I am using
non-blocking sockets which are bound to different IP addresses in a
round-robin manner, and to port 0, so the kernel can choose a free
local port.

Now I observed that I am getting EADDRINUSE errors on the bind system
call, even though there should be ports left according to the current
net.ipv4.ip_local_port_range sysctl setting.

I tried to enumerate the used ports at the time of the error using
netstat, which shows only rather few ports being in use, but I
realize that this is an inaccurate measure because it takes time for
netstat to be forked and run.

What I wonder is: Is there any limit beyond
net.ipv4.ip_local_port_range which may lead to EADDRINUSE errors?
Maybe any limits in the kernel data structures I should be aware of
when working with huge amounts of TCP connections?

Thanks!

--
Steven

--
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/