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.103706.68156515.davem@davemloft.net>
Date:	Tue, 06 Mar 2007 10:37:06 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	gerrit@....abdn.ac.uk
Cc:	netdev@...r.kernel.org, weid@...css.fujitsu.com
Subject: Re: [NET]: Please revert disallowing zero listen queues

From: Gerrit Renker <gerrit@....abdn.ac.uk>
Date: Tue, 6 Mar 2007 13:32:09 +0000

> Please can you reconsider the patch regarding the accept_queue
> 
> http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.22.git;a=commit;h=8488df894d05d6fa41c2bd298c335f944bb0e401
> 
> It disallows to set a `backlog' argument to listen(2) of zero. Using
> a zero backlog is often done (e.g. ttcp), and disallowing a zero 
> backlog will break many applications. I had to recode several applications
> which rely on this convention.
> 
> The problem further spreads from TCP to DCCP (same behaviour).
> 
> Below is a patch to revert this change.

Everything I've ever seen clearly states that a backlog of
zero means that zero connections are allowed.

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 :-)
-
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