question about fh_copy

question about fh_copy

[Ming Zhang]

Hi All

A question about fh_copy(). This function is called many times on
argument passed directly from nfs clients. If a malicious nfs client
forge a fh, then fh_copy can invoke oops quite easily. shall we always
call fh_verify before call fh_copy? Thanks!

Ming

-- 
http://blackmagic02881.wordpress.com/


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: question about fh_copy

[J. Bruce Fields]

On Sat, Jan 27, 2007 at 10:20:08AM -0500, Ming Zhang wrote:
> A question about fh_copy(). This function is called many times on
> argument passed directly from nfs clients. If a malicious nfs client
> forge a fh, then fh_copy can invoke oops quite easily.

I don't see how; can you explain?

--b.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: question about fh_copy

[Ming Zhang]

On Sun, 2007-01-28 at 18:01 -0500, J. Bruce Fields wrote:
> On Sat, Jan 27, 2007 at 10:20:08AM -0500, Ming Zhang wrote:
> > A question about fh_copy(). This function is called many times on
> > argument passed directly from nfs clients. If a malicious nfs client
> > forge a fh, then fh_copy can invoke oops quite easily.
> 
> I don't see how; can you explain?

svc_process at http://lxr.linux.no/source/net/sunrpc/svc.c?v=2.6.18#L386
invoke a rpc processing function, for example, nfsd3_proc_getattr
then at http://lxr.linux.no/source/fs/nfsd/nfs3proc.c?v=2.6.18#L64
invoke fh_copy before fh_verify. since src coming from client, client
can forge a fh to let code
http://lxr.linux.no/source/include/linux/nfsd/nfsfh.h?v=2.6.18#L222 get
executed. if fh_dentry is a invalid pointer, it can get oops.

or think in another way, if the fh will always be valid with all
contents, then what is the point to call fh_verify to do "sanity checks
on the dentry in a client file handle", quoted from fh_verify comment at
http://lxr.linux.no/source/fs/nfsd/nfsfh.c?v=2.6.18#L105?

Ming

> 
> --b.
-- 
http://blackmagic02881.wordpress.com/


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: question about fh_copy

[J. Bruce Fields]

On Sun, Jan 28, 2007 at 07:36:39PM -0500, Ming Zhang wrote:
> On Sun, 2007-01-28 at 18:01 -0500, J. Bruce Fields wrote:
> > On Sat, Jan 27, 2007 at 10:20:08AM -0500, Ming Zhang wrote:
> > > A question about fh_copy(). This function is called many times on
> > > argument passed directly from nfs clients. If a malicious nfs client
> > > forge a fh, then fh_copy can invoke oops quite easily.
> > 
> > I don't see how; can you explain?
> 
> svc_process at http://lxr.linux.no/source/net/sunrpc/svc.c?v=2.6.18#L386
> invoke a rpc processing function, for example, nfsd3_proc_getattr
> then at http://lxr.linux.no/source/fs/nfsd/nfs3proc.c?v=2.6.18#L64
> invoke fh_copy before fh_verify. since src coming from client, client
> can forge a fh to let code
> http://lxr.linux.no/source/include/linux/nfsd/nfsfh.h?v=2.6.18#L222 get
> executed. if fh_dentry is a invalid pointer, it can get oops.

The fh_dentry field does not contain client-provided data; look at
nfs3xdr.c:decode_fh() to see how the svc_fh structure is initialized.

--b.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: question about fh_copy

[Ming Zhang]

On Sun, 2007-01-28 at 20:04 -0500, J. Bruce Fields wrote:
> On Sun, Jan 28, 2007 at 07:36:39PM -0500, Ming Zhang wrote:
> > On Sun, 2007-01-28 at 18:01 -0500, J. Bruce Fields wrote:
> > > On Sat, Jan 27, 2007 at 10:20:08AM -0500, Ming Zhang wrote:
> > > > A question about fh_copy(). This function is called many times on
> > > > argument passed directly from nfs clients. If a malicious nfs client
> > > > forge a fh, then fh_copy can invoke oops quite easily.
> > > 
> > > I don't see how; can you explain?
> > 
> > svc_process at http://lxr.linux.no/source/net/sunrpc/svc.c?v=2.6.18#L386
> > invoke a rpc processing function, for example, nfsd3_proc_getattr
> > then at http://lxr.linux.no/source/fs/nfsd/nfs3proc.c?v=2.6.18#L64
> > invoke fh_copy before fh_verify. since src coming from client, client
> > can forge a fh to let code
> > http://lxr.linux.no/source/include/linux/nfsd/nfsfh.h?v=2.6.18#L222 get
> > executed. if fh_dentry is a invalid pointer, it can get oops.
> 
> The fh_dentry field does not contain client-provided data; look at
> nfs3xdr.c:decode_fh() to see how the svc_fh structure is initialized.

my fault. in decode_fh, it only copy fh_handle. i read it too fast and
thought it copy the whole svc_fh.

sorry for the noise.



> 
> --b.
-- 
http://blackmagic02881.wordpress.com/


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

rpc.gssd segfault on FC5 client

[Jim Davis]

I'm trying to set up Kerberized NFSv3 between a Network Appliance NFS 
server and a Fedora Core 5 and 6 clients, following the outline in 
http://www.netapp.com/library/tr/3481.pdf.  FC6 is working, but trying 
to start rpc.gssd on FC5 fails as the daemon dies with a segmentation fault:

Script started on Mon Jan 29 13:23:46 2007
angora$ cd /
angora$ uname -r
2.6.18-1.2257.fc5smp
angora$ rpm -qf /usr/sbin/rpc.gssd
nfs-utils-1.0.8-4.fc5
angora$ sudo /usr/kerberos/sbin/ktutil
ktutil:  read_kt /etc/krb5.keytab
ktutil:  l -e
slot KVNO Principal
---- ---- 
---------------------------------------------------------------------
    1    3 nfs/angora.cs.arizona.edu@CS.ARIZONA.EDU (DES cbc mode with 
CRC-32)
ktutil:  angora$
angora$ sudo sh-c "ulimit -c unlimited;/usr/sbin/rpc.gssd -f -vvv"
Using keytab file '/etc/krb5.keytab'
Processing keytab entry for principal 
'nfs/angora.cs.arizona.edu@CS.ARIZONA.EDU'
We will use this entry (nfs/angora.cs.arizona.edu@CS.ARIZONA.EDU)
sh: line 1:  9479 Segmentation fault      (core dumped) 
/usr/sbin/rpc.gssd -f -vvv
angora$ sudo gdb /usr/lib/debug/usr/sbin/rpc.gssd.debug /core.9479
GNU gdb Red Hat Linux (6.3.0.0-1.134.fc5rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host 
libthread_db library "/lib/libthread_db.so.1".


warning: core file may not match specified executable file.
Failed to read a valid object file image from memory.
Core was generated by `/usr/sbin/rpc.gssd -f -vvv'.
Program terminated with signal 11, Segmentation fault.
#0  0x00428d58 in ?? ()
(gdb) bt
#0  0x00428d58 in ?? ()
#1  0x00000004 in ?? ()
#2  0x08019c78 in ?? ()
#3  0x0042cdc9 in ?? ()
#4  0x08019c00 in ?? ()
#5  0xbfb4f27c in ?? ()
#6  0x00c34918 in ?? ()
#7  0x00471e00 in ?? ()
#8  0x08019c2c in ?? ()
#9  0x00000018 in ?? ()
#10 0x00000001 in ?? ()
#11 0xbfb4f25c in ?? ()
#12 0xbfb4f258 in ?? ()
#13 0xbfb4f240 in ?? ()
#14 0x08019c60 in ?? ()
#15 0xbfb4f204 in ?? ()
#16 0xbfb4f1f8 in ?? ()
#17 0xbfb4f228 in ?? ()
#18 0x08019c08 in ?? ()
#19 0xbfb4f178 in ?? ()
#20 0x08019c38 in ?? ()
#21 0xbfb4f300 in ?? ()
#22 0x007abc0e in ?? ()
---Type <return> to continue, or q <return> to quit---
#23 0xbfb4f2f0 in ?? ()
#24 0x007abb91 in ?? ()
#25 0x080169a0 in ?? ()
#26 0x00000028 in ?? ()
#27 0xbfb4f178 in ?? ()
#28 0x00000000 in ?? ()
(gdb) angora$
angora$ exit
exit

Script done on Mon Jan 29 13:25:13 2007
angora$

Any ideas on what I've missed, or how to get more useful information out 
of the core dump?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Kevin Coffman]

On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
> I'm trying to set up Kerberized NFSv3 between a Network Appliance NFS
> server and a Fedora Core 5 and 6 clients, following the outline in
> http://www.netapp.com/library/tr/3481.pdf.  FC6 is working, but trying
> to start rpc.gssd on FC5 fails as the daemon dies with a segmentation fault:

[snip]

> Any ideas on what I've missed, or how to get more useful information out
> of the core dump?

Hmmm,

Interesting.  I'll assume from the addresses listed in gdb that this
is a 32-bit machine.  It looks like the binaries are stripped, so I'm
not sure what we could get from the dump.

I assume you have all the pre-reqs or it wouldn't start.  Just poking
around.  What do the following show?
"rpm -qa | grep nfs"
"rpm -qa | grep krb"

What are the contents of /etc/gssapi_mech.conf?

K.C.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Jim Davis]

Kevin Coffman wrote:
> 
> I assume you have all the pre-reqs or it wouldn't start.  Just poking
> around.  What do the following show?
> "rpm -qa | grep nfs"
> "rpm -qa | grep krb"
> 
> What are the contents of /etc/gssapi_mech.conf?


angora$ rpm -qa | grep nfs
nfs-utils-1.0.8-4.fc5
nfs-utils-lib-1.0.8-4.FC5
system-config-nfs-1.3.19-1
nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2
angora$ rpm -qa | grep krb
krb5-devel-1.4.3-5.3
krbafs-devel-1.2.2-9.2.1
krb5-server-1.4.3-5.3
krb5-workstation-1.4.3-5.3
krbafs-1.2.2-9.2.1
krb5-auth-dialog-0.6.cvs20060212-1.1
krb5-libs-1.4.3-5.3
pam_krb5-2.2.6-2.2
krbafs-utils-1.2.2-9.2.1
angora$ cat /etc/gssapi_mech.conf
# Example /etc/gssapi_mech.conf file
#
# GSSAPI Mechanism Definitions
#
# This configuration file determines which GSS-API mechanisms
# the gssd code should use
#
# NOTE:
# The initiaiization function "mechglue_internal_krb5_init"
# is used for the MIT krb5 gssapi mechanism.  This special
# function name indicates that an internal function should
# be used to determine the entry points for the MIT gssapi
# mechanism funtions.
#
# library                               initialization function
# ================================      ==========================
# The MIT K5 gssapi library, use special function for initialization.
libgssapi_krb5.so.2             mechglue_internal_krb5_init
#
# The SPKM3 gssapi library function.  Use the function spkm3_gss_initialize.
# /usr/local/gss_mechs/spkm/spkm3/libgssapi_spkm3.so    spkm3_gss_initialize



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Kevin Coffman]

I'm not seeing nfs-utils-debuginfo available.  What is included with
nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?

On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
> Kevin Coffman wrote:
> >
> > I assume you have all the pre-reqs or it wouldn't start.  Just poking
> > around.  What do the following show?
> > "rpm -qa | grep nfs"
> > "rpm -qa | grep krb"
> >
> > What are the contents of /etc/gssapi_mech.conf?
>
>
> angora$ rpm -qa | grep nfs
> nfs-utils-1.0.8-4.fc5
> nfs-utils-lib-1.0.8-4.FC5
> system-config-nfs-1.3.19-1
> nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2
> angora$ rpm -qa | grep krb
> krb5-devel-1.4.3-5.3
> krbafs-devel-1.2.2-9.2.1
> krb5-server-1.4.3-5.3
> krb5-workstation-1.4.3-5.3
> krbafs-1.2.2-9.2.1
> krb5-auth-dialog-0.6.cvs20060212-1.1
> krb5-libs-1.4.3-5.3
> pam_krb5-2.2.6-2.2
> krbafs-utils-1.2.2-9.2.1

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Jim Davis]

Kevin Coffman wrote:
> I'm not seeing nfs-utils-debuginfo available.  What is included with
> nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?

Oh, right, I downloaded that rpm to another system and tarred the 
contents across to this one.  (That system had the same problem but I 
decided to focus on just this one.)  The rpm is supposed to have 
debuggable versions of the nfs-utils in it:

korat$ rpm -ql nfs-utils-debuginfo
/usr/lib/debug/sbin/rpc.lockd.debug
/usr/lib/debug/sbin/rpc.statd.debug
/usr/lib/debug/usr/sbin/exportfs.debug
/usr/lib/debug/usr/sbin/nfsstat.debug
/usr/lib/debug/usr/sbin/nhfsstone.debug
/usr/lib/debug/usr/sbin/rpc.gssd.debug
/usr/lib/debug/usr/sbin/rpc.idmapd.debug
/usr/lib/debug/usr/sbin/rpc.mountd.debug
/usr/lib/debug/usr/sbin/rpc.nfsd.debug
/usr/lib/debug/usr/sbin/rpc.svcgssd.debug
/usr/lib/debug/usr/sbin/showmount.debug
/usr/src/debug/nfs-utils-1.0.8-rc2
/usr/src/debug/nfs-utils-1.0.8-rc2/support
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/client.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/export.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/hostname.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/mount.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/mount_xdr.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/nfsctl.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/rmtab.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/export/xtab.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/exportfs.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/gssapi
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/gssapi/gssapi.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/ha-callout.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/misc.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/mount.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/nfs
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/nfs/nfs.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/nfslib.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/rpcmisc.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/xio.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/include/xlog.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/misc
/usr/src/debug/nfs-utils-1.0.8-rc2/support/misc/mountpoint.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/cacheio.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/closeall.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/exports.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/getfh.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/lockdsvc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/nfsclient.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/nfsctl.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/nfsexport.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/nfssvc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/rmtab.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/rpcdispatch.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/rpcmisc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/svc_socket.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/wildmat.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/xio.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/xlog.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/nfs/xmalloc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include/rpc
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include/rpc/auth.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include/rpc/auth_gss.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include/rpc/clnt.h
/usr/src/debug/nfs-utils-1.0.8-rc2/support/rpc/include/rpc/xdr.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/exportfs
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/exportfs/exportfs.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/context.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/err_util.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gss_oids.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gss_oids.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gss_util.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gss_util.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gssd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gssd.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gssd_main_loop.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/gssd_proc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/krb5_util.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/krb5_util.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/gssd/write_bytes.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/atomicio.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/cfg.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/cfg.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/idmapd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/nfs_idmap.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/setproctitle.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/strlcat.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/idmapd/strlcpy.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/lockd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/lockd/lockd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/auth.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/cache.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/mount_dispatch.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/mountd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/mountd.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/rmtab.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/mountd/svc_run.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nfsd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nfsd/nfsd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nfsstat
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nfsstat/nfsstat.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nhfsstone
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/nhfsstone/nhfsstone.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/showmount
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/showmount/showmount.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/callback.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/log.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/misc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/monitor.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/notify.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/notlist.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/notlist.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/rmtcall.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/simu.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/sm_inter.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/sm_inter_clnt.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/sm_inter_svc.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/sm_inter_xdr.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/stat.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/statd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/statd.h
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/state.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/statd/svc_run.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/cacheio.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/context.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/err_util.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/gss_oids.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/gss_util.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/svcgssd.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/svcgssd_main_loop.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/svcgssd_mech2file.c
/usr/src/debug/nfs-utils-1.0.8-rc2/utils/svcgssd/svcgssd_proc.c
korat$


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Kevin Coffman]

On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
> Kevin Coffman wrote:
> > I'm not seeing nfs-utils-debuginfo available.  What is included with
> > nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?
>
> Oh, right, I downloaded that rpm to another system and tarred the
> contents across to this one.  (That system had the same problem but I
> decided to focus on just this one.)  The rpm is supposed to have
> debuggable versions of the nfs-utils in it:

So it looks like running /usr/lib/debug/usr/sbin/rpc.gssd.debug might
give us a backtrace to work with?

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Jim Davis]

Kevin Coffman wrote:
> On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
>> Kevin Coffman wrote:
>> > I'm not seeing nfs-utils-debuginfo available.  What is included with
>> > nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?
>>
>> Oh, right, I downloaded that rpm to another system and tarred the
>> contents across to this one.  (That system had the same problem but I
>> decided to focus on just this one.)  The rpm is supposed to have
>> debuggable versions of the nfs-utils in it:
> 
> So it looks like running /usr/lib/debug/usr/sbin/rpc.gssd.debug might
> give us a backtrace to work with?

Well, I'm not really clear on how the debuginfo stuff is supposed to be 
used, but it doesn't seem that I can run that file directly.  The best I 
could come up with after googling around is that it's meant to fed to 
gdb to analyze core dumps from the real executable.  But it's quite 
possible I'm missing something there...

sh-3.1# ls -l /usr/lib/debug/usr/sbin/rpc.gssd.debug
-rwxr-xr-x 1 root root 60564 Feb 12  2006 
/usr/lib/debug/usr/sbin/rpc.gssd.debug
sh-3.1# /usr/lib/debug/usr/sbin/rpc.gssd.debug -f
sh: /usr/lib/debug/usr/sbin/rpc.gssd.debug: Permission denied




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: rpc.gssd segfault on FC5 client

[Kevin Coffman]

On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
> Kevin Coffman wrote:
> > On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
> >> Kevin Coffman wrote:
> >> > I'm not seeing nfs-utils-debuginfo available.  What is included with
> >> > nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?
> >>
> >> Oh, right, I downloaded that rpm to another system and tarred the
> >> contents across to this one.  (That system had the same problem but I
> >> decided to focus on just this one.)  The rpm is supposed to have
> >> debuggable versions of the nfs-utils in it:
> >
> > So it looks like running /usr/lib/debug/usr/sbin/rpc.gssd.debug might
> > give us a backtrace to work with?
>
> Well, I'm not really clear on how the debuginfo stuff is supposed to be
> used, but it doesn't seem that I can run that file directly.  The best I
> could come up with after googling around is that it's meant to fed to
> gdb to analyze core dumps from the real executable.  But it's quite
> possible I'm missing something there...
>
> sh-3.1# ls -l /usr/lib/debug/usr/sbin/rpc.gssd.debug
> -rwxr-xr-x 1 root root 60564 Feb 12  2006
> /usr/lib/debug/usr/sbin/rpc.gssd.debug
> sh-3.1# /usr/lib/debug/usr/sbin/rpc.gssd.debug -f
> sh: /usr/lib/debug/usr/sbin/rpc.gssd.debug: Permission denied

I'll see if I can find that rpm and figure out how to make use of it...

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs