Lines Matching refs:it

48 and whilst it is open, a cache is at least partially in existence.  The daemon
49 opens this and sends commands down it to control the cache.
54 the filesystem, shrinking the cache by culling the objects it contains to make
55 space if necessary - see the "Cache Culling" section.  This means it can be
131 configures the cache and tells it to begin caching.  At that point the cache
226 their atimes have changed or if the kernel module says it is still using them.
233 The CacheFiles module will create two directories in the directory it was
241 kernel module moves any retired or culled objects that it can't simply unlink
260 If an object has children, then it will be represented as a directory.
274 If the key is so long that it exceeds NAME_MAX with the decorations added on to
275 it, then it will be cut into pieces, the first few of which will be used to
306 Note that CacheFiles will erase from the cache any file it doesn't recognise or
317 One of the problems that CacheFiles faces is that it is generally acting on
326 security context of the process when it the target of an operation performed by
330 When the CacheFiles module is asked to bind to its cache, it:
333      that as the security label with which it will create files.  By default,
343      and asks LSM to supply a security ID as which it should act given the
358 The module's security ID gives it permission to create, move and remove files
363 The daemon's security ID gives it only a very restricted set of permissions: it
365 not read or write files in the cache, and so it is precluded from accessing the
366 data cached therein; nor is it permitted to create new files in the cache.
391 By default, the cache is located in /var/fscache, but if it is desirable that
392 it should be elsewhere, than either the above policy files must be altered, or
410 its own task_security structure, and redirects current->cred to point to it
411 when it acts on behalf of another process, in that process's context.
413 The reason it does this is that it calls vfs_mkdir() and suchlike rather than
428 This means it may lose signals or ptrace events for example, and affects what
456 then it will gather certain statistics and display them through a proc file.