Hi All,
We have also observed the similar backtrace in our own custom FSAL layer running Ganesha
version 2.5.5.
Unfortunately, core-dump is not available to debug further.
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f7d69a89330]
/lib/x86_64-linux-gnu/libpthread.so.0(pthread_rwlock_wrlock+0xa)[0x7f7d69a84cca]
/usr/bin/ganesha.nfsd(fsal_obj_handle_fini+0x22)[0x41db65]
/usr/bin/ganesha.nfsd[0x527d08]
/usr/bin/ganesha.nfsd(_mdcache_lru_unref+0x72f)[0x52cc37]
/usr/bin/ganesha.nfsd[0x526a08]
/usr/bin/ganesha.nfsd[0x528355]
/usr/bin/ganesha.nfsd[0x52887c]
/usr/bin/ganesha.nfsd(mdcache_lru_get+0x15)[0x52c03b]
/usr/bin/ganesha.nfsd[0x53b6c6]
/usr/bin/ganesha.nfsd(mdcache_new_entry+0x1ff)[0x53d0bd]
/usr/bin/ganesha.nfsd(mdcache_locate_host+0x351)[0x53e212]
/usr/bin/ganesha.nfsd(mdcache_create_handle+0x4b)[0x5368ae]
/usr/bin/ganesha.nfsd(nfs3_FhandleToCache+0x111)[0x4f1161]
/usr/bin/ganesha.nfsd(nfs3_read+0x21d)[0x494438]
/usr/bin/ganesha.nfsd(nfs_rpc_execute+0x1ee2)[0x44bfef]
/usr/bin/ganesha.nfsd[0x44c749]
/usr/bin/ganesha.nfsd[0x500f58]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f7d69a81184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7d6935837d