Lines Matching refs:locking

13 0. Why you should avoid mandatory locking
32 1. What is  mandatory locking?
35 Mandatory locking is kernel enforced file locking, as opposed to the more usual
36 cooperative file locking used to guarantee sequential access to files among
47 "advisory" locking scheme. However, the world isn't perfect, and there's
51 with a "mandatory" locking scheme, whereby the operating system kernel would
56 The System V mandatory locking scheme was intended to have as little impact as
58 as candidates for mandatory locking, and using the existing fcntl()/lockf()
64       the whole truth. System V locking is based on fcntl(). The granularity of
65       fcntl() is such that it allows the locking of byte ranges in files, in
66       addition to entire files, so the mandatory locking rules also have byte
69    2. POSIX.1 does not specify any scheme for mandatory locking, despite
70       borrowing the fcntl() locking scheme from System V. The mandatory locking
73 2. Marking a file for mandatory locking
76 A file is marked as a candidate for mandatory locking by setting the group-id
90 I have considered the implementations of mandatory locking available with
111 In my opinion only MAP_SHARED mappings should be immune from locking, and then
125 1. Mandatory locks can only be applied via the fcntl()/lockf() locking
159 for the purposes of mandatory locking.
181 Mandatory locking is disabled on all filesystems by default, and must be
185 Since kernel v4.5, it is possible to disable mandatory locking