Lines Matching refs:that

34 CacheFiles is a caching backend that's meant to use as a cache a directory on
42 filesystem providing the backing services.  Note that CacheFiles does not
46 CacheFiles creates a misc character device - "/dev/cachefiles" - that is used
78 It is strongly recommended that the "dir_index" option is enabled on Ext3
131 configures the cache and tells it to begin caching.  At that point the cache
163 kernel module contains its own very cut-down path walking facility that ignores
187 discarding objects from the cache that have been used less recently than
220 Note that these are percentages of available space and available files, and do
241 kernel module moves any retired or culled objects that it can't simply unlink
245 anything that appears therein.
249 "J...".  Note that the "cache/" directory is itself a special index.
253 directory, data objects will have a file in the directory called "data" that
274 If the key is so long that it exceeds NAME_MAX with the decorations added on to
283 Note that keys are raw data, and not only may they exceed NAME_MAX in size,
288 "base-64" encode ones that aren't directly suitable.  The two versions of
300 Each object in the cache has an extended attribute label that holds the object
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
318 behalf of a process, and running in that process's context, and that includes a
319 security context that is not appropriate for accessing the cache - either
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
325 fsgid and actor security label) that the process acts as - without changing the
333      that as the security label with which it will create files.  By default,
373 and later versions.  In that tarball, see the files:
391 By default, the cache is located in /var/fscache, but if it is desirable that
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
420 parameters with that object is created (UID, GID, security label) would be
421 derived from that process that issued the system call, thus potentially
425 What is required is to temporarily override the security of the process that
427 security data as that affects the process as an object, not just as a subject.
443 LSM hooks exist that allow SELinux (or Smack or whatever) to reject a request
474      Each row shows the number of events that took a particular range of times.