From: Mike Fedyk <mfedyk@matchmail.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Matthew Wilcox <willy@debian.org>,
linux-fsdevel@vger.kernel.org,
"Joseph D. Wagner" <theman@josephdwagner.info>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Does mandatory locking need to be set when the file is locked?
Date: Tue, 16 Dec 2003 12:33:03 -0800 [thread overview]
Message-ID: <20031216203303.GA1402@matchmail.com> (raw)
In-Reply-To: <OF46ABFCA2.D4CF20F4-ON87256DFE.00692D4E-88256DFE.0069943C@us.ibm.com>
On Tue, Dec 16, 2003 at 11:13:36AM -0800, Bryan Henderson wrote:
> I don't mean to be argumentative, but discussions like this lead me to
> suspect that the reason no one is using mandatory locks is _because_ they
> don't work. So while it's true that fixing them won't fix a bunch of
I tend to agree.
> So anyone else considering finding a viable way to make mandatory range
> locks work (or even just get closer to working than they are now) should
> not be discouraged.
Another problem, is that with standard network filesystems (read NFS < 4)
the suggestive locks aren't propagated unless you use lock files!
What linux needs is to stop using stateless network filesystems. While they
have their upsides, they do have their downsides.
next prev parent reply other threads:[~2003-12-16 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 1:57 Does mandatory locking need to be set when the file is locked? Joseph D. Wagner
2003-12-15 15:38 ` Matthew Wilcox
2003-12-15 15:50 ` Joseph D. Wagner
2003-12-15 16:23 ` Randy.Dunlap
2003-12-15 18:09 ` Trond Myklebust
2003-12-15 18:59 ` Matthew Wilcox
2003-12-16 19:13 ` Bryan Henderson
2003-12-16 20:33 ` Mike Fedyk [this message]
2003-12-16 21:48 ` Trond Myklebust
2003-12-16 22:00 ` Mike Fedyk
2003-12-15 17:05 ` Bryan Henderson
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=20031216203303.GA1402@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=theman@josephdwagner.info \
--cc=trond.myklebust@fys.uio.no \
--cc=willy@debian.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.