public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: "David J. Wilder" <dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [ewg] rping is not resolving ipv6 addresses
Date: Mon, 12 Oct 2009 13:47:58 -0600	[thread overview]
Message-ID: <20091012194758.GB20313@obsidianresearch.com> (raw)
In-Reply-To: <1255369979.29677.7.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>

On Mon, Oct 12, 2009 at 10:52:59AM -0700, David J. Wilder wrote:

> > It is not, IPv6 link local addresses must be scoped. rping is
> > parsing the address with getaddrinfo, that does correctly set the
> > sin6_scope_id value in the sockaddr.
> 
> ping6 is scoping the address (setting sin6_scope_id) by hand. So rping
> should do the same thing.

getaddrinfo already sets sin6_scope_id. Newish iputils ping6 also uses
getaddrinfo and doesn't touch the sin6_scope_id except in some
specialized cases.

> > So this is two bugs in the rdma cm, rping is correct as is..
> 
> It may be correct, but not functional with link-local address.

Like I said, the RDMA CM kernel component has the bugs, not rping..

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-10-12 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1254957121.23471.17.camel@wilder.ibm.com>
     [not found] ` <adavdiqn63u.fsf@cisco.com>
     [not found]   ` <1255114672.3533.8.camel@wilder.ibm.com>
     [not found]     ` <1255114672.3533.8.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-09 20:53       ` [ewg] rping is not resolving ipv6 addresses Or Gerlitz
     [not found]         ` <15ddcffd0910091353w51bddc60w8452ca107de296fb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-09 21:15           ` David J. Wilder
     [not found]             ` <1255122901.3533.20.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-09 21:22               ` Or Gerlitz
2009-10-09 22:46               ` Jason Gunthorpe
     [not found]                 ` <20091009224604.GG5191-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-10-09 23:02                   ` Sean Hefty
     [not found]                     ` <0AA9B9870A0545E6BCCF3A5EF4BAB34E-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-10-11  7:29                       ` Or Gerlitz
     [not found]                         ` <4AD18944.1040404-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2009-10-11 19:52                           ` Jason Gunthorpe
2009-10-12 17:52                   ` [ewg] " David J. Wilder
     [not found]                     ` <1255369979.29677.7.camel-XfwDJb4SXxnMbYB6QlFGEg@public.gmane.org>
2009-10-12 19:47                       ` Jason Gunthorpe [this message]

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=20091012194758.GB20313@obsidianresearch.com \
    --to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
    --cc=dwilder-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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