Trond Myklebust wrote:
I'm surprised that we can get into this state, though. How is sys_umount() able to exit with either readaheads or writebacks still pending? Is this perhaps occurring on a lazy umount?
Should we be submitting async tasks in gss_destroying_context? I get this problem on umount with 3 or more cached GSS creds -- and end up blocked in rpciod_down - destroy_workqueue..
With short expiry, dcache (or something) holds a ref, and these creds stack up, then all queue tasks to clear context on shutdown.
Ben Coddington - To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
