public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: [PATCH] gssd: have gssd deal with scopeid field in upcall
Date: Fri, 11 Dec 2009 16:22:33 -0500	[thread overview]
Message-ID: <4B22B819.6090504@RedHat.com> (raw)
In-Reply-To: <1260305091-19523-1-git-send-email-jlayton@redhat.com>



On 12/08/2009 03:44 PM, Jeff Layton wrote:
> Recent kernels (2.6.32) have started displaying the scopeid for some
> addresses in the upcall. gssd doesn't know how to deal with them. Change
> gssd to use getaddrinfo instead of inet_pton since that can deal with
> scopeid's in addresses. That also allows us to elminate the port
> conversion in read_service_info.
> 
> If getaddrinfo returns an address with a non-zero sin6_scope_id however,
> reject it. getnameinfo ignores that field and just uses the sin6_addr
> part when resolving. But, two addresses that differ only in
> sin6_scope_id could refer to completely different hosts.
> 
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
Committed... 

I tested this at the same time at the same time I tested Chuck's
mounting patches... 

steved.

      parent reply	other threads:[~2009-12-11 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 20:44 [PATCH] gssd: have gssd deal with scopeid field in upcall Jeff Layton
2009-12-09 18:50 ` J. Bruce Fields
2009-12-09 19:10   ` Jeff Layton
     [not found]     ` <20091209141049.61e8fb0b-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2009-12-09 20:16       ` J. Bruce Fields
2009-12-09 20:45         ` Jeff Layton
2009-12-11 21:22 ` Steve Dickson [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=4B22B819.6090504@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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