NFS locking does not call the filesystem lock operation

dixonbp@us.ibm.com
Tue, 18 Jul 2000 14:06:00 -0400

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Roger Larsson: "[PATCH--] test5-pre1 vmfix (rev 2.1) + one rescheduling bugfix?"
Previous message: Andrew van der Stock: "[patch] 2.4.0-test5-pre2, linux/arch/alpha/kernel/osf_sys.c"

NFS locking routines (nlmsvc_lock and others in svclock.c) go directly to
the
default kernel operations (eg., posix_lock_file) and do not invoke any
filesystem
lock operation that may have been provided. Why don't they execute the
lock
file_operation (if one exists for the filesystem) similarly to the non-NFS
fcntl_setlk which does the following:

if (filp->f_op->lock != NULL) {
error = filp->f_op->lock(filp, cmd, &file_lock);

Without this, a filesystem that needs to provide the lock operation has no
way to achieve proper locking via nfs clients.

-------
Brian Dixon
dixonbp@us.ibm.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Roger Larsson: "[PATCH--] test5-pre1 vmfix (rev 2.1) + one rescheduling bugfix?"
Previous message: Andrew van der Stock: "[patch] 2.4.0-test5-pre2, linux/arch/alpha/kernel/osf_sys.c"