From: Andi Kleen <andi@firstfloor.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>, netdev <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: follow-up: discrepancy with POSIX
Date: Wed, 19 Sep 2007 19:26:53 +0200 [thread overview]
Message-ID: <20070919172653.GB18045@one.firstfloor.org> (raw)
In-Reply-To: <46F15305.2030507@redhat.com>
On Wed, Sep 19, 2007 at 09:49:09AM -0700, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andi Kleen wrote:
> > The standard way to undo connect is to use AF_UNSPEC. Code to handle
> > that for dgram sockets is there. It's the same code for v4 and v6.
>
> I quoted the standard and it does not say anything about AF_UNSPEC. So
> you cannot simply make such broad statements.
Ok "standard" was perhaps a poor choice of words.
AF_UNSPEC used to be introduced long ago by Alan based on some early
POSIX draft iirc.
Also incidentially it's a null address:
include/linux/socket.h:#define AF_UNSPEC 0
> But the spec calls for a "null address" to be used and that's in my
> understanding something different from using AF_UNSPEC.
memset(&sockaddr, 0, sizeof(sockaddr)) should give you AF_UNSPEC
-Andi
next prev parent reply other threads:[~2007-09-19 17:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 15:21 follow-up: discrepancy with POSIX Ulrich Drepper
2007-09-19 15:47 ` Andi Kleen
2007-09-19 16:49 ` Ulrich Drepper
2007-09-19 16:52 ` David Miller
2007-09-19 17:04 ` Ulrich Drepper
2007-09-19 17:27 ` Ulrich Drepper
2007-09-19 17:26 ` Andi Kleen [this message]
2007-09-19 17:46 ` Ulrich Drepper
2007-09-19 17:57 ` Andi Kleen
2007-09-19 18:02 ` Ulrich Drepper
2007-09-19 18:30 ` Andi Kleen
2007-09-19 18:38 ` Rick Jones
2007-09-19 19:40 ` Andi Kleen
2007-09-19 20:33 ` Valdis.Kletnieks
2007-09-19 18:06 ` Alan Cox
2007-09-19 16:15 ` David Miller
2007-09-19 16:39 ` 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=20070919172653.GB18045@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).