It seems that nfsd can return reply attributes with a link count of zero but without an NFS3ERR_STALE status. We've seen this actually happen for a write request to a file with a single link that is concurrently being removed without NLM lock protection. What is the proper behavior here? -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
