linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steve Dickson <SteveD@redhat.com>,
	libtirpc List <libtirpc-devel@lists.sourceforge.net>,
	Thorsten Kukuk <kukuk@suse.de>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: New libtirpc vs fedfs-utils.
Date: Mon, 25 May 2015 12:12:23 +1000	[thread overview]
Message-ID: <20150525121223.0c9d2cd6@notabene.brown> (raw)
In-Reply-To: <A2BEDA4A-5064-4715-A49B-ABA7247BF7DB@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Fri, 22 May 2015 10:25:20 -0400 Chuck Lever <chuck.lever@oracle.com> wrote:

> Hi Neil-
> 
> 
> On May 21, 2015, at 11:54 PM, NeilBrown <neilb@suse.de> wrote:
> 
> > 
> > 
> > Hi Chuck / Steve,
> > 
> > It seems that fedfs-utils doesn't build with the new libtirpc.
> > 
> > Specifically fedfsd requires symbols
> > 
> >  svcauth_gss_set_svc_name
> >  svcauth_gss_get_principal
> > 
> > but libtirpc doesn't expose them any longer - it never included them in .h
> > files or provided documentation.
> > 
> > As far as I can tell fedfs-utils really does need these interfaces, there is
> > no alternate.
> 
> fedfs-utils needs to be updated, now that the new rpc_gss API is merged
> into libtirpc, to use rpc_gss_set_svc_name(3t) and rpc_gss_getcred(3t).
> That’s on my to-do list.
> 
> In the meantime . . .
> 
> > Would it be appropriate to make them "official" with header and doco support?
> 
> A fix for this issue was proposed yesterday on libtirpc-devel.
> 

Ahh, thanks.  I should have looked in the archives first, shouldn't I ?

I'll go see.

Thanks,
NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2015-05-25  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  3:54 New libtirpc vs fedfs-utils NeilBrown
2015-05-22 14:25 ` Chuck Lever
2015-05-25  2:12   ` NeilBrown [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=20150525121223.0c9d2cd6@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=kukuk@suse.de \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs@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).