netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:57:00 +0200	[thread overview]
Message-ID: <20070919175700.GC18045@one.firstfloor.org> (raw)
In-Reply-To: <46F1608E.7060908@redhat.com>

On Wed, Sep 19, 2007 at 10:46:54AM -0700, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Andi Kleen wrote:
> >> 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
> 
> But the spec calls for <quote>null address for the protocol</quote>.
> 
> That means the family for the null address is the same as the family of
> the socket.

Spec doesn't match traditional behaviour then. IPv4 0.0.0.0 is 
traditionally an synonym for old style all broadcast (255.255.255.255) 
on UDP/RAW and it's certainly possible to connect() to that. 

-Andi

  reply	other threads:[~2007-09-19 17:57 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
2007-09-19 17:46       ` Ulrich Drepper
2007-09-19 17:57         ` Andi Kleen [this message]
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=20070919175700.GC18045@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).