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

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] [day] [month] [year] [list]

Message-ID: <24732.1180604497@redhat.com>
Date:	Thu, 31 May 2007 10:41:37 +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 [try #2]

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

> > Yes.  I need to get the server lock first, before going to the VFS locking
> > routines.
> 
> That doesn't really answer the question.  The NFS client has similar
> requirements, but it doesn't have to duplicate the per-inode lists of
> granted locks, for example.

Actually, it might...  It's just that they're in the lock manager server, not
in the NFS client.

As far as I can tell, NFS passes each lock request individually to the lock
manager server, which grants them individually.  AFS doesn't do that.

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/