Linux filesystem development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: "Joseph D. Wagner" <theman@josephdwagner.info>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Does mandatory locking need to be set when the file is locked?
Date: Mon, 15 Dec 2003 15:38:58 +0000	[thread overview]
Message-ID: <20031215153858.GE15674@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200312150757.57021.theman@josephdwagner.info>

On Mon, Dec 15, 2003 at 07:57:57AM +0600, Joseph D. Wagner wrote:
> I'm writing a program that changes the permissions on a file to enable 
> mandatory locking, does its thing to the file, and then resets the 
> permissions.
> 
> Do do the mandatory locking permissions have to be set before the lock is 
> set? Or will the kernel dynamically recognize the change on the fly so that 
> an active lock becomes mandatory?

Please, don't use mandatory locking.  It's racy (by design), buggy
(by design) and adds code to the fast path.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2003-12-15 15:38 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 [this message]
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
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=20031215153858.GE15674@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=theman@josephdwagner.info \
    /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