From: Lukas Hejtmanek <xhejtman@gmail.com>
To: Fred Isaman <faisaman4@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: local_lock mount option
Date: Thu, 13 Dec 2012 15:23:36 +0100 [thread overview]
Message-ID: <20121213142336.GP10897@ics.muni.cz> (raw)
In-Reply-To: <CADnza44SJ0JZN05OtMZcjsm+NwdMVPGTa2f2vG9TbpUJR_B4Zw@mail.gmail.com>
On Thu, Dec 13, 2012 at 09:10:14AM -0500, Fred Isaman wrote:
> local_lock is a v2/v3 option. It does not currently effect the behavior of v4.
if I understand correctly source codes, it should:
nfs/file.c:
const struct file_operations nfs4_file_operations = {
[...]
.lock = nfs_lock,
.flock = nfs_flock,
and nfs_(f)lock contains tests for:
NFS_MOUNT_LOCAL_FCNTL
NFS_MOUNT_LOCAL_FLOCK
but for some reason, it is not propageted from mount call. Dunno why. Or am
I something missing?
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2012-12-13 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 13:35 local_lock mount option Lukas Hejtmanek
2012-12-13 14:10 ` Fred Isaman
2012-12-13 14:23 ` Lukas Hejtmanek [this message]
2012-12-13 14:38 ` Fred Isaman
2012-12-13 14:40 ` Lukas Hejtmanek
2012-12-13 14:48 ` Fred Isaman
2012-12-13 14:56 ` Lukas Hejtmanek
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=20121213142336.GP10897@ics.muni.cz \
--to=xhejtman@gmail.com \
--cc=faisaman4@gmail.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 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).