public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pierre Habouzit <pierre.habouzit@intersec.com>,
	Wei Yongjun <yjwei@cn.fujitsu.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sctp: if backlog is 0, listening shall not be deactivated.
Date: Wed, 14 Jan 2009 10:53:23 -0500	[thread overview]
Message-ID: <496E0A73.9030903@hp.com> (raw)
In-Reply-To: <20090114152133.675da27b@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> SCTP API simply chooses to ignore the "may".  It is still fully compliant
>> with POSIX in this regard.
> 
> Linux chooses the interpretation that zero means one connection. Having a
> single protocol variant do different things is not nice because  a lot
> of code is designed to handle multiple address families and expect the
> same non address handling behaviour.
> 
> So while it may be able to claim posix compliance, its not Linux
> behaviour, and its relying on a specific interpretation of posix not
> being used by the OS.
> 
> At the very least the current behaviour of the SCTP code is plain rude.
> 

I will submit a requirest to change this behavior in the spec, but I am not
terribly optimistic.  This has been specified for a very long time and there
might be applications taking advantage of the ability to shut listing off.

At this time, let's leave this as is.  A well written application should specify
the listen backlog anyway, otherwise it's depending on the "may" language in the
Posix spec and will not get consistent behavior across different systems.

-vlad

  reply	other threads:[~2009-01-14 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  9:42 [PATCH] sctp: if backlog is 0, listening shall not be deactivated Pierre Habouzit
2009-01-14 13:17 ` Vlad Yasevich
2009-01-14 13:21   ` Alan Cox
2009-01-14 13:36     ` Vlad Yasevich
2009-01-14 15:21       ` Alan Cox
2009-01-14 15:53         ` Vlad Yasevich [this message]
2009-01-14 16:37           ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496E0A73.9030903@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.habouzit@intersec.com \
    --cc=yjwei@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox