linux-kernel - Re: [PATCH] sctp: if backlog is 0, listening shall not be deactivated.

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: <496DEA60.2080700@hp.com>
Date:	Wed, 14 Jan 2009 08:36:32 -0500
From:	Vlad Yasevich <vladislav.yasevich@...com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Pierre Habouzit <pierre.habouzit@...ersec.com>,
	Wei Yongjun <yjwei@...fujitsu.com>,
	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sctp: if backlog is 0, listening shall not be deactivated.

Alan Cox wrote:
>> However SCTP API explicitly states that when the backlog is 0, listening is
>> disabled.  Here is an excerpt from the draft describing this:
> 
> POSIX is an established standard, SCTP is a draft proposal. POSIX should
> win. The SCTP developers need to bring their draft API into alignment with
> POSIX.
> 
> They need to fix their draft to use a sockopt or similar to
> enable/disable listening.
> 

Here is what POSIX says:

A backlog argument of 0 may allow the socket to accept connections, in which
case the length of the listen queue may be set to an implementation-defined
minimum value.


SCTP API simply chooses to ignore the "may".  It is still fully compliant
with POSIX in this regard.

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