Lines Matching refs:is
6 JFFS2. It is not expected to remain perfectly up to date, but ought to
13 The alloc_sem is a per-filesystem mutex, used primarily to ensure
14 contiguous allocation of space on the medium. It is automatically
24 which they belong. This is for the benefit of NAND flash - adding new
33 the alloc_sem is also used to protect the wbuf-related members of the
35 if the wbuf is currently holding any data is permitted, though.
43 This is the JFFS2-internal equivalent of the inode mutex i->i_sem.
48 The reason that the i_sem itself isn't used for this purpose is to
59 mutex, which is obtained by the garbage collection code and also
74 This is used to serialise access to the eraseblock lists, to the
76 (NB) the per-inode list of physical nodes. The latter is a special
84 Note that the per-inode list of physical nodes (f->nodes) is a special
90 long as the pointer you're holding is to a _valid_ node, not an
93 The erase_completion_lock is also used to protect the c->gc_task
107 This spinlock also covers allocation of new inode numbers, which is
112 will not be removed. So, it is allowed to access it without locking
124 This mutex is only used by the erase code which frees obsolete node
128 discarded or whether it is still required to show that an inode has
133 collection code is looking at them.
144 which indicates which flash region (if any) is currently covered by
156 In read-only path, write-semaphore is too much exclusion. It's enough
161 of those objects. Thus, a series of processes is often required to retry,
162 when updating such a object is necessary under holding read semaphore.