Linux filesystem development
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-fsdevel@vger.kernel.org,
	"Joseph D. Wagner" <theman@josephdwagner.info>
Subject: Re: Does mandatory locking need to be set when the file is locked?
Date: Tue, 16 Dec 2003 14:00:12 -0800	[thread overview]
Message-ID: <20031216220012.GD1402@matchmail.com> (raw)
In-Reply-To: <1071611329.2098.27.camel@nidelv.trondhjem.org>

On Tue, Dec 16, 2003 at 04:48:49PM -0500, Trond Myklebust wrote:
> P? ty , 16/12/2003 klokka 15:33, skreiv Mike Fedyk:
> > Another problem, is that with standard network filesystems (read NFS < 4)
> > the suggestive locks aren't propagated unless you use lock files!
> 
> Huh? If by 'suggestive' locks you mean advisory locks, then the above is
> pure FUD.
> 

I stand corrected.

> The Linux NFS implementation has been stateful ever since 2.2.0, when
> Olaf added full support for POSIX byte-range locks for v2 and v3 over
> the standard NLM protocol.
> Nobody has yet used it in order to implement support for BSD locks, but
> that is at least partly because it would break with the "standard"
> behaviour that BSD locks and POSIX locks should not see each other
> (remember those "sendmail" bugs a couple of years ago?).

Oh, the joys of netatalk using flock, and samba using fcntl... :(

> All NFSv4 adds of value when it comes to locking is support for
> mandatory locking, and a faster, more robust protocol than NLM ever was.
> Otherwise the combination NFSv3 w/ NLM has been keeping most people's
> mailboxes safe for several years now...

I'm very happy to hear this.

Thanks

  reply	other threads:[~2003-12-16 22:00 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
2003-12-16 21:48             ` Trond Myklebust
2003-12-16 22:00               ` Mike Fedyk [this message]
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=20031216220012.GD1402@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=theman@josephdwagner.info \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox