From: NeilBrown <neilb@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>, Steve Dickson <SteveD@redhat.com>
Cc: libtirpc-devel@lists.sourceforge.net,
Thorsten Kukuk <kukuk@suse.de>,
linux-nfs@vger.kernel.org
Subject: New libtirpc vs fedfs-utils.
Date: Fri, 22 May 2015 13:54:42 +1000 [thread overview]
Message-ID: <20150522135442.048de45d@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
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.
Would it be appropriate to make them "official" with header and doco support?
A simple hack is:
--- libtirpc-0.3.0.orig/src/libtirpc.map
+++ libtirpc-0.3.0/src/libtirpc.map
@@ -284,4 +284,6 @@ TIRPC_PRIVATE {
__libc_clntudp_bufcreate;
# private, but used by rpcbind:
__svc_clean_idle; svc_auth_none; libtirpc_set_debug;
+ # private, but used by fedfsd:
+ svcauth_gss_set_svc_name; svcauth_gss_get_principal;
};
but I suspect something better is really needed.
Are there other server-side routines that need to be exported?
Thanks,
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next reply other threads:[~2015-05-22 3:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 3:54 NeilBrown [this message]
2015-05-22 14:25 ` New libtirpc vs fedfs-utils Chuck Lever
2015-05-25 2:12 ` NeilBrown
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=20150522135442.048de45d@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).