vfs_lock_file(9) [centos man page]

VFS_LOCK_FILE(9)						   The Linux VFS						  VFS_LOCK_FILE(9)

NAME

       vfs_lock_file - file byte range lock

SYNOPSIS

       int vfs_lock_file(struct file * filp, unsigned int cmd, struct file_lock * fl, struct file_lock * conf);

ARGUMENTS

       filp
	   The file to apply the lock to

       cmd
	   type of locking operation (F_SETLK, F_GETLK, etc.)

       fl
	   The lock to be applied

       conf
	   Place to return a copy of the conflicting lock, if found.

DESCRIPTION

       A caller that doesn't care about the conflicting lock may pass NULL as the final argument.

       If the filesystem defines a private ->lock method, then conf will be left unchanged; so a caller that cares should initialize it to some
       acceptable default.

       To avoid blocking kernel daemons, such as lockd, that need to acquire POSIX locks, the ->lock interface may return asynchronously, before
       the lock has been granted or denied by the underlying filesystem, if (and only if) lm_grant is set. Callers expecting ->lock to return
       asynchronously will only use F_SETLK, not F_SETLKW; they will set FL_SLEEP if (and only if) the request is for a blocking lock. When ->lock
       does return asynchronously, it must return FILE_LOCK_DEFERRED, and call ->lm_grant when the lock request completes. If the request is for
       non-blocking lock the file system should return FILE_LOCK_DEFERRED then try to get the lock and call the callback routine with the result.
       If the request timed out the callback routine will return a nonzero return code and the file system should release the lock. The file
       system is also responsible to keep a corresponding posix lock when it grants a lock so the VFS can find out which locks are locally held
       and do the correct lock cleanup when required. The underlying filesystem must not drop the kernel lock or call ->lm_grant before returning
       to the caller with a FILE_LOCK_DEFERRED return code.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							  VFS_LOCK_FILE(9)

Check Out this Related Man Page

simple_lock_try(9r)													       simple_lock_try(9r)

NAME

       simple_lock_try - General: Tries to assert a simple lock

SYNOPSIS

       #include <kern/lock.h>

       boolean_t simple_lock_try(
	       simple_lock_t slock_ptr );

ARGUMENTS

       Specifies a pointer to a simple lock structure. You can declare this simple lock structure by using the decl_simple_lock_data routine.

DESCRIPTION

       The  simple_lock_try  routine tries to assert a lock with read and write access for the resource associated with the specified simple lock.
       The main difference between this routine and simple_lock is that simple_lock_try returns immediately if the  resource  is  already  locked,
       while  simple_lock  spins until the lock has been obtained. Thus, call simple_lock_try when you need a simple lock but the code cannot spin
       until the lock is obtained.

       To release a simple lock successfully asserted by simple_lock_try, call the simple_unlock routine.

RETURN VALUES

       The simple_lock_try routine returns one of the following values: The simple_lock_try routine successfully asserted the  simple  lock.   The
       simple_lock_try routine failed to assert the simple lock.

FILES

SEE ALSO

       Routines: decl_simple_lock_data(9r), simple_lock(9r), simple_lock_init(9r), simple_lock_terminate(9r), simple_unlock(9r)

       Data Structures: slock(9s)

															       simple_lock_try(9r)

Linux and UNIX Man Pages

vfs_lock_file(9) [centos man page]

Check Out this Related Man Page