From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au, aeb@cwi.nl
Subject: Re: sendmsg and IP_PKTINFO
Date: 19 Feb 2003 09:17:58 +0100 [thread overview]
Message-ID: <p73wujwy98p.fsf@amdsimf.suse.de> (raw)
In-Reply-To: "David S. Miller"'s message of "19 Feb 2003 01:20:15 +0100"
"David S. Miller" <davem@redhat.com> writes:
> All you are showing us Neil is that the documentation
> is inaccurate. That snippet you showed me from manual
> pages is wrong about sendmsg semantics.
Yes, it's wrong I agree. Here is a patch. Please check
and if nobody complains Andries can apply.
>
> The ifindex you specify does mean "send out this interface".
>
> It is very surprising that this documentation is wrong since
> the likely author (Andi Kleen) is smart enough to read the
> actual implementation when he writes these things.
There was no serious technical review of these manpages ever, so
I wouldn't be surprised if there are more such technical errors (hint ;)
-Andi
--- ip.7~ 2003-02-19 08:50:48.000000000 +0100
+++ ip.7 2003-02-19 09:09:36.000000000 +0100
@@ -260,12 +260,16 @@
.I IP_PKTINFO
is passed to
.BR sendmsg (2)
-then the outgoing packet will be sent over the interface
-specified in
-.B ipi_ifindex
-with the destination address set to
+and
+.\" This field is grossly misnamed
.B ipi_spec_dst
-.
+is not zero then it is used as the local source address for the routing
+table lookup and for setting up IP source route options.
+When
+.B ipi_ifindex
+is not zero the primary local address of the interface specified by the index overwrites
+.I ipi_spec_dst
+for the routing table lookup.
.TP
.B IP_RECVTOS
next parent reply other threads:[~2003-02-19 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15954.4693.893707.471216@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
[not found] ` <200302181606.TAA03838@sex.inr.ac.ru.suse.lists.linux.kernel>
[not found] ` <15954.49970.860809.75554@notabene.cse.unsw.edu.au.suse.lists.linux.kernel>
[not found] ` <20030218.155651.108799644.davem@redhat.com.suse.lists.linux.kernel>
2003-02-19 8:17 ` Andi Kleen [this message]
2003-02-19 8:06 ` sendmsg and IP_PKTINFO David S. Miller
2003-02-21 3:51 ` Neil Brown
2003-02-21 4:17 ` David S. Miller
2003-02-18 19:57 Julian Anastasov
2003-02-18 23:39 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2003-02-15 1:53 Neil Brown
2003-02-18 7:10 ` David S. Miller
2003-02-18 11:00 ` sendmsg and IP_PKTINFO Neil Brown
2003-02-18 16:06 ` kuznet
2003-02-18 23:35 ` Neil Brown
2003-02-18 23:56 ` David S. Miller
2003-02-19 3:52 ` David S. Miller
2003-02-19 4:13 ` Neil Brown
2003-02-19 4:03 ` David S. Miller
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=p73wujwy98p.fsf@amdsimf.suse.de \
--to=ak@suse.de \
--cc=aeb@cwi.nl \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.