This is why I've never bothered to fix the crashes when
desrtoy_fsals() finds things; it's an indication to me that something
is leaking refs.

On Tue, Dec 12, 2017 at 7:55 PM, Frank Filz <ffilz...@mindspring.com> wrote:
>> I was testing code I'd written over the weekend, but it segfaulted on
>> shutdown after running pynfs (pynfs itself was successful.)  No problems
>> simply starting and pkilling without doing any work.
>>
>> Gradually backed things out, until I'm at the 1a75e52 V2.6-dev.20, but
> still
>> seeing the problem on shutdown.  Ran it twice to be sure.  Took quite a
> bit of
>> time to run pynfs over and over.
>
> Ok, so I've fixed the crash, but looking at some debug, the reason we are
> getting to where it could crash is that we are leaking export references.
> I'm doing some code examination and finding export and obj_handle reference
> leaks... So far they are all in NFS v4.
>
> I hope to post some patches early tomorrow.
>
> It would really help if things that expected everything to cleanup actually
> checked if everything was cleaned up...
>
> destroy_fsals should never find any exports to call shutdown_export on.
>
> Frank
>
>> Error: couldn't complete write to the log file
>> /home/bill/rdma/install/var/log/ganesha.log status=9 (Bad file descriptor)
>> message was:
>> 11/12/2017 19:13:01 : epoch 5a2f193a : simpson91 : ganesha.nfsd-
>> 13288[Admin] rpc :TIRPC :DEBUG :svc_destroy_it() 0x61900008bb80 fd 19
>> xp_refs 1 af 0 port 4294967295 @ svc_xprt_shutdown:364
>>
>> Thread 271 "ganesha.nfsd" received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 0x7fff68053700 (LWP 31096)]
>> 0x00007fffef8ca739 in release (exp_hdl=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/FSAL_VFS/export.c:79
>> 79            LogDebug(COMPONENT_FSAL, "Releasing VFS export for
>> %s",
>> (gdb) bt
>> #0  0x00007fffef8ca739 in release (exp_hdl=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/FSAL_VFS/export.c:79
>> #1  0x000000000044799d in shutdown_export (export=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/fsal_destroyer.c:152
>> #2  0x0000000000447d66 in destroy_fsals ()
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/fsal_destroyer.c:194
>> #3  0x000000000047d9c3 in do_shutdown ()
>>      at /home/bill/rdma/nfs-ganesha/src/MainNFSD/nfs_admin_thread.c:511
>> #4  0x000000000047de09 in admin_thread (UnusedArg=0x0)
>>      at /home/bill/rdma/nfs-ganesha/src/MainNFSD/nfs_admin_thread.c:531
>> #5  0x00007ffff60b373a in start_thread (arg=0x7fff68053700)
>>      at pthread_create.c:333
>> #6  0x00007ffff598ae7f in clone ()
>>      at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
>> (gdb) quit
>> A debugging session is active.
>>
>>       Inferior 1 [process 30823] will be killed.
>>
>> Quit anyway? (y or n) y
>> [root@simpson91 install]#
>>
>>
>> Thread 270 "ganesha.nfsd" received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 0x7fff68087700 (LWP 6650)]
>> 0x00007fffef8ca739 in release (exp_hdl=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/FSAL_VFS/export.c:79
>> 79            LogDebug(COMPONENT_FSAL, "Releasing VFS export for
>> %s",
>> (gdb) bt
>> #0  0x00007fffef8ca739 in release (exp_hdl=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/FSAL_VFS/export.c:79
>> #1  0x000000000044799d in shutdown_export (export=0x61300000cec0)
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/fsal_destroyer.c:152
>> #2  0x0000000000447d66 in destroy_fsals ()
>>      at /home/bill/rdma/nfs-ganesha/src/FSAL/fsal_destroyer.c:194
>> #3  0x000000000047d9c3 in do_shutdown ()
>>      at /home/bill/rdma/nfs-ganesha/src/MainNFSD/nfs_admin_thread.c:511
>> #4  0x000000000047de09 in admin_thread (UnusedArg=0x0)
>>      at /home/bill/rdma/nfs-ganesha/src/MainNFSD/nfs_admin_thread.c:531
>> #5  0x00007ffff60b373a in start_thread (arg=0x7fff68087700)
>>      at pthread_create.c:333
>> #6  0x00007ffff5989e7f in clone ()
>>      at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
>> (gdb) quit
>> A debugging session is active.
>>
>>       Inferior 1 [process 6378] will be killed.
>>
>> Quit anyway? (y or n) y
>> [root@simpson91 install]#
>>
>>
>>
>>
> ----------------------------------------------------------------------------
> --
>> Check out the vibrant tech community on one of the world's most engaging
>> tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nfs-ganesha-devel mailing list
>> Nfs-ganesha-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to