From: Ed Goggin <egoggin@vmware.com>
To: linux-nfs@vger.kernel.org
Subject: stale or not stale
Date: Thu, 2 Aug 2012 18:57:58 -0700 (PDT) [thread overview]
Message-ID: <1781697815.4540720.1343959078882.JavaMail.root@vmware.com> (raw)
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?
next reply other threads:[~2012-08-03 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 1:57 Ed Goggin [this message]
2012-08-03 2:29 ` stale or not stale Andrei Warkentin
2012-08-03 10:52 ` Jeff Layton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1781697815.4540720.1343959078882.JavaMail.root@vmware.com \
--to=egoggin@vmware.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.