netdev - Re: [Bugme-new] [Bug 13688] New: backlog parameter of listen is not working with TCP

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

Message-ID: <20090701211003.GC19223@Chamillionaire.breakpoint.cc>
Date:	Wed, 1 Jul 2009 23:10:03 +0200
From:	Florian Westphal <fw@...len.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	netdev@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, florent.cloirec@...e.fr
Subject: Re: [Bugme-new] [Bug 13688] New: backlog parameter of listen is
	not working with TCP

Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed, 1 Jul 2009 18:39:07 GMT
> bugzilla-daemon@...zilla.kernel.org wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=13688
> >            Summary: backlog parameter of listen is not working with TCP
> >            Product: Networking
[..]
> > When creating a server I usually create a socket, bind it to any address and
> > call listen to limit the queue size, then I call accept in a loop to handle
> > clients one by one.
> > 
> > In a particular case I wanted to serve only 1 client and refuse the other
> > connection attempts. I tried any value for the backlog parameter, whatever I
> > use the server is not refusing any connection, though the queue should be full.
> > The SYN+ACK handshake is completed everytime.

The behaviour depends on net.ipv4.tcp_abort_on_overflow sysctl.
If its on, new connections are reset once the backlog is exhausted.
--
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