From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Michael Kerrisk <mtk-lkml@gmx.net>
Cc: Peter Chubb <peterc@gelato.unsw.edu.au>,
linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
michael.kerrisk@gmx.net
Subject: Re: fcntl(F GETLEASE) semantics??
Date: Thu, 11 Aug 2005 07:51:45 -0400 [thread overview]
Message-ID: <1123761105.8251.10.camel@lade.trondhjem.org> (raw)
In-Reply-To: <19888.1123748055@www44.gmx.net>
to den 11.08.2005 Klokka 10:14 (+0200) skreiv Michael Kerrisk:
> No. The behavior in Linux recently, and arbitrarily (IMO) changed:
The change was NOT arbitrary. It was deliberate and for the reasons
stated.
The whole point of leases is to support CIFS oplocks for Samba and NFSv4
delegations in the kernel. Both have the same specific expected
behaviour.
The original deviates from that expected behaviour by allowing you to
get a shared lease when in a condition that does not allow actual
sharing.
Cheers,
Trond
next prev parent reply other threads:[~2005-08-11 11:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 23:48 fcntl(F_GETLEASE) semantics?? Peter Chubb
2005-08-11 1:14 ` Trond Myklebust
2005-08-11 1:29 ` Peter Chubb
2005-08-11 8:14 ` fcntl(F GETLEASE) semantics?? Michael Kerrisk
2005-08-11 11:51 ` Trond Myklebust [this message]
2005-08-11 12:27 ` Michael Kerrisk
2005-08-11 12:49 ` Trond Myklebust
2005-08-11 13:22 ` Michael Kerrisk
2005-08-11 14:06 ` Trond Myklebust
2005-08-11 14:12 ` Trond Myklebust
2005-08-11 14:20 ` J. Bruce Fields
2005-08-11 14:42 ` Michael Kerrisk
2005-08-11 14:40 ` Michael Kerrisk
2005-08-11 15:06 ` Trond Myklebust
2005-08-11 15:25 ` Trond Myklebust
2005-08-11 14:10 ` Stephen Rothwell
2005-08-11 18:41 ` fcntl(F_GETLEASE) semantics?? Heikki Orsila
2005-08-11 18:56 ` Trond Myklebust
2005-08-11 19:02 ` Heikki Orsila
2005-08-11 19:15 ` Trond Myklebust
2005-08-11 19:23 ` Heikki Orsila
2005-08-11 19:31 ` Trond Myklebust
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=1123761105.8251.10.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@gmx.net \
--cc=peterc@gelato.unsw.edu.au \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®