From: Peter Staubach <staubach@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Horman <nhorman@redhat.com>, nfs@lists.sourceforge.net
Subject: Re: Should fcntl operations check attributes with the server when NFS shares are mounted noac?
Date: Thu, 23 Feb 2006 15:50:49 -0500 [thread overview]
Message-ID: <43FE2029.7040205@redhat.com> (raw)
In-Reply-To: <1140725969.7963.17.camel@lade.trondhjem.org>
Trond Myklebust wrote:
>>I would disagree somewhat. There is a customer who has stumbled into this
>>situation. We know that there is a bug here, that it has affected at one
>>customer, and the risk for fixing it is very small. The gains might not be
>>obvious, but it would make at one customer even slightly happier. That's
>>worth the small amount of effort that it would take to fix this.
>>
>>
>
>Will the customer be happy to find out that the application breaks in
>much more nefarious ways as a result of a non-working lease?
>
>If this is Samba, then the correct answer is obvious: turn off oplocks
>in the configuration file since they won't ever work as expected anyway.
>
Well, it may or may not break, actually. I would think that it would depend
upon what assumptions were being made by the application.
I would still suggest that the cost of fixing something which is clearly
broken is outweighed by the benefit of making a customer, at least
temporarily,
happy. If that customer is porting something from a system does support
F_SETLEASE, such as Solaris, and was happy with the way that it worked
there,
then they may be happy with the current support of F_SETLEASE in Linux.
It is even possible that they were using leases for some reason instead of
file/record locking. Who knows? :-)
Thanx...
ps
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-02-23 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 12:42 Should fcntl operations check attributes with the server when NFS shares are mounted noac? Neil Horman
2006-02-23 13:36 ` Peter Staubach
2006-02-23 15:17 ` Neil Horman
2006-02-23 16:12 ` Trond Myklebust
2006-02-23 19:22 ` Neil Horman
2006-02-23 19:39 ` Trond Myklebust
2006-02-23 19:50 ` Peter Staubach
2006-02-23 20:19 ` Trond Myklebust
2006-02-23 20:50 ` Peter Staubach [this message]
2006-02-23 22:31 ` Trond Myklebust
2006-02-24 14:06 ` Neil Horman
2006-02-24 14:26 ` Trond Myklebust
2006-02-24 15:25 ` Neil Horman
2006-02-24 15:39 ` 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=43FE2029.7040205@redhat.com \
--to=staubach@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=nhorman@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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.