netdev - Re: [NET]: Please revert disallowing zero listen queues

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]

Message-Id: <20070306.111142.07639258.davem@davemloft.net>
Date:	Tue, 06 Mar 2007 11:11:42 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	rick.jones2@...com
Cc:	gerrit@....abdn.ac.uk, netdev@...r.kernel.org,
	weid@...css.fujitsu.com
Subject: Re: [NET]: Please revert disallowing zero listen queues

From: Rick Jones <rick.jones2@...com>
Date: Tue, 06 Mar 2007 10:54:00 -0800

> > So we're not "disallowing" a backlog argument of zero to
> > listen().  We'll accept that just fine, the only thing that
> > happens is that you'll get what you ask for, that being
> > no connections :-)
> 
> I'm not sure where HP-UX inherited the 0 = 1 bit - perhaps from BSD, nor 
> am I sure there is official chapter and verse, but:
> 
> <excerpt>
> backlog is limited to the range of 0 to SOMAXCONN, which is 	defined in 
> <sys/socket.h>.  SOMAXCONN is currently set to 4096.  If any other 
> value is specified, the system automatically assigns the closest value 
>      within the range.  A backlog of 0 specifies only 1 pending 
> connection      is allowed at any given time.
> </excerpt>
> 
> I don't have a Solaris, BSD or AIX manpage for listen handy to check 
> them but would not be surprised to see they are similar.

Ok, that seals the deal for me, I'll revert the change :)
-
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