From: David Howells <dhowells@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] AFS: Implement file locking
Date: Tue, 29 May 2007 10:34:41 +0100 [thread overview]
Message-ID: <28654.1180431281@redhat.com> (raw)
In-Reply-To: <20070527161252.GA12804@fieldses.org>
J. Bruce Fields <bfields@fieldses.org> wrote:
> You can contrive examples of applications that would be correct given
> the standard fcntl behavior, but that would deadlock on a system that
> didn't allow read locks to jump the queue in the above situation.
Yes, but you can also contrive starvation if you allow locks to jump the
queue. Obviously, the Linux kernel behaviour is to allow readlocks to jump
the queue if a readlock is currently in force, so I have to conform to that,
whether I like it or not.
I'll need to test the upgrade/downgrade case. I don't know whether the AFS
server supports that. If it doesn't, I can emulate downgrade, but not upgrade
- not unless I only ever ask it for exclusive locks.
Lock upgrading is really, really easy to contrive deadlock for.
David
next prev parent reply other threads:[~2007-05-29 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 16:55 [PATCH] AFS: Implement file locking David Howells
2007-05-25 7:31 ` Jiri Slaby
2007-05-26 2:23 ` J. Bruce Fields
2007-05-26 3:11 ` Kyle Moffett
2007-05-27 0:12 ` David Howells
2007-05-26 23:55 ` David Howells
2007-05-27 2:25 ` J. Bruce Fields
2007-05-27 8:51 ` David Howells
2007-05-27 16:12 ` J. Bruce Fields
2007-05-29 9:34 ` David Howells [this message]
2007-05-29 20:08 ` J. Bruce Fields
2007-05-29 12:43 ` David Howells
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=28654.1180431281@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).