From: Francois-Xavier KOWALSKI <francois-xavier_kowalski@hp.com>
To: Linux-Kernel Mailing-List <linux-kernel@vger.kernel.org>
Subject: [2.4.14] wrong IPv4 listen syscall return code
Date: Wed, 21 Nov 2001 14:28:26 +0100 [thread overview]
Message-ID: <3BFBABFA.9040200@hp.com> (raw)
Hello kernel developpers,
(please Cc: me in reply, since I am not on the ML).
I am puzzled my a problem around the listen(2) system call.
The man page states the following item, which make sense:
ERRORS
EADDRINUSE
Another socket is already listening on the same
port.
EBADF The argument s is not a valid descriptor.
ENOTSOCK
The argument s is not a socket.
EOPNOTSUPP
The socket is not of a type that supports the lis
ten operation.
But when I go within the source code of listen implementation for STREAM
protocol (as specified for TCL in net/ipv4/af_inet.c) in the function
inet_listen() the default return code is EINVAL instead of EOPNOTSUPP.
Who holds the truth? I believe source code is wrong, since EOPNOTSUPP is
much more explicit.
BTW, where is the official & as much up-to-date as possible source for
kernel syscalls man pages?
--
Francois-Xavier "FiX" KOWALSKI
reply other threads:[~2001-11-21 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BFBABFA.9040200@hp.com \
--to=francois-xavier_kowalski@hp.com \
--cc=linux-kernel@vger.kernel.org \
/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