linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 13:43:29 +0100	[thread overview]
Message-ID: <11388.1180442609@redhat.com> (raw)
In-Reply-To: <20070527161252.GA12804@fieldses.org>

J. Bruce Fields <bfields@fieldses.org> wrote:

> > At the moment, yes.  Don't the POSIX and flock lock-handling routines in the
> > kernel normally do that anyway?
> 
> No, they'd upgrade in that case.

I just checked.  The OpenAFS server supports neither lock upgrading nor lock
downgrading.  Attempts to do either incur an abort with code 0x02f6df0a
(which I believe to be equivalent to EAGAIN).

This means that I can't practically support lock upgrading.  Lock downgrading
I can emulate by handing apparent readlocks to local processes whilst holding
a writelock on the server.

David

      parent reply	other threads:[~2007-05-29 12:44 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
2007-05-29 20:08       ` J. Bruce Fields
2007-05-29 12:43     ` David Howells [this message]

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=11388.1180442609@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).