From: Vitaliy Gusev <gusev.vitaliy@nexenta.com>
To: <trond.myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: question about lost lock during reclaimation
Date: Fri, 18 May 2012 14:49:55 +0400 [thread overview]
Message-ID: <4FB62953.9000701@nexenta.com> (raw)
Hello, Trond!
Could you point to idea how userspace process can know about
lost lock on NFSv4 server (due to server reboot) ?
See "case -NFS4ERR_DENIED" at nfs4_reclaim_locks():
http://lxr.free-electrons.com/source/fs/nfs/nfs4state.c#L1184
---
Thanks,
Vitaliy
reply other threads:[~2012-05-18 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FB62953.9000701@nexenta.com \
--to=gusev.vitaliy@nexenta.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).