linux-kernel - Re: [PATCH] AFS: Implement file locking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <11388.1180442609@redhat.com>
Date:	Tue, 29 May 2007 13:43:29 +0100
From:	David Howells <dhowells@...hat.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] AFS: Implement file locking

J. Bruce Fields <bfields@...ldses.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/