Lines Matching refs:in
38 reaping stale nodes and culling. This is called cachefilesd and lives in
44 filesystems are very specific in nature.
48 and whilst it is open, a cache is at least partially in existence. The daemon
66 available in the system and in the cache filesystem:
74 - bmap() support on files in the filesystem (FIBMAP ioctl).
86 The cache is configured by a script in /etc/cachefilesd.conf. These commands
108 Specify a tag to FS-Cache to use in distinguishing multiple caches.
113 Specify a numeric bitmask to control debugging in the kernel module.
166 Do not create, rename or unlink files and directories in the cache whilst the
169 Renaming files in the cache might make objects appear to be other objects (the
175 Do not create files or directories in the cache, lest the cache get confused or
178 Do not chmod files in the cache. The module creates things with minimal
189 directories are culled if not in use.
192 percentage of files available in the underlying filesystem. There are six
198 If the amount of free space and the number of available files in the cache
204 If the amount of available space or the number of available files in the
210 If the amount of available space or the number of available files in the
224 These are then culled in least recently used order. A new scan of the cache is
225 started as soon as space is made in the table. Objects will be skipped if
233 The CacheFiles module will create two directories in the directory it was
240 The active cache objects all reside in the first directory. The CacheFiles
253 directory, data objects will have a file in the directory called "data" that
261 Immediately in the representative directory are a collection of directories
283 Note that keys are raw data, and not only may they exceed NAME_MAX in size,
300 Each object in the cache has an extended attribute label that holds the object
302 the netfs. The latter is used to detect stale objects in the cache and update
318 behalf of a process, and running in that process's context, and that includes a
320 because the files in the cache are inaccessible to that process, or because if
321 the process creates a file in the cache, that file may be inaccessible to other
349 based on a rule of this form in the policy.
359 and directories in the cache, to find and access directories and files in the
361 write files in the cache.
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.
369 There are policy source files available in:
391 By default, the cache is located in /var/fscache, but if it is desirable that
397 located elsewhere when SELinux is in enforcing mode, please see:
402 in the sources.
409 CacheFiles makes use of the split security in the task_struct. It allocates
411 when it acts on behalf of another process, in that process's context.
416 circumstances the caching code is running in the security context of whatever
426 issued the system call. We can't, however, just do an in-place change of the
429 the process looks like in /proc.
431 So CacheFiles makes use of a logical split in the security between the
434 is never overridden. This is what appears in /proc, and is what is used when a
444 for CacheFiles to run in a context of a specific security label, or to create
475 Each step is 1 jiffy in size. The JIFS column indicates the particular
484 debugging enabled by adjusting the value in: