Lines Matching +full:directory +full:- +full:based
11 ------------------------------------------------------------------------------
16 The files in this directory can be used to tune and monitor
31 aio-nr & aio-max-nr
32 -------------------
34 ``aio-nr`` shows the current system-wide number of asynchronous io
35 requests. ``aio-max-nr`` allows you to change the maximum value
36 ``aio-nr`` can grow to. If ``aio-nr`` reaches ``aio-nr-max`` then
38 ``aio-max-nr`` does not result in the
39 pre-allocation or re-sizing of any kernel data structures.
41 dentry-negative
42 ----------------------------
47 dentry-state
48 ------------
75 they help speeding up rejection of non-existing files provided
79 file-max & file-nr
80 ------------------
82 The value in ``file-max`` denotes the maximum number of file-
89 ``file-nr`` denote the number of allocated file handles, the number
92 file handles -- this is not an error, it just means that the
96 Attempts to allocate more file descriptors than ``file-max`` are
99 VFS: file-max limit <number> reached
104 inode-nr & inode-state
105 ----------------------
110 The file ``inode-nr`` contains the first two items from
111 ``inode-state``, so we'll skip to that file...
113 ``inode-state`` contains three actual numbers and four dummies.
126 mount-max
127 ---------
134 -------
136 This denotes the maximum number of file-handles a process can
143 -------------------------
145 Some filesystems only support 16-bit UIDs and GIDs, although in Linux
154 pipe-user-pages-hard
155 --------------------
157 Maximum total number of pages a non-privileged user may allocate for pipes.
163 pipe-user-pages-soft
164 --------------------
166 Maximum total number of pages a non-privileged user may allocate for pipes
176 ---------------
179 an attacker-controlled FIFO, where a program expected to create a regular
186 owner of the directory.
190 This protection is based on the restrictions in Openwall.
194 --------------------
196 A long-standing class of security issues is the hardlink-based
197 time-of-check-time-of-use race, most commonly seen in world-writable
210 This protection is based on the restrictions in Openwall and grsecurity.
214 -----------------
217 avoids writes to an attacker-controlled regular file, where a program
224 owned by the owner of the directory.
230 ------------------
232 A long-standing class of security issues is the symlink-based
233 time-of-check-time-of-use race, most commonly seen in world-writable
238 https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=/tmp
243 a sticky world-writable directory, or when the uid of the symlink and
244 follower match, or when the directory owner matches the symlink's owner.
246 This protection is based on the restrictions in Openwall and grsecurity.
250 -------------
266 :ref:`Documentation/admin-guide/sysctl/kernel.rst <core_pattern>`)
269 details on this limitation, see CVE-2006-2451.) This mode is
273 care, or specific directory defined for catching core dumps.
285 in Documentation/admin-guide/binfmt-misc.rst.
288 3. /proc/sys/fs/mqueue - POSIX message queues filesystem
294 API (as noted by the MSG tag in the POSIX 1003.1-2001 version of the System
324 4. /proc/sys/fs/epoll - Configuration options for the epoll interface
327 This directory contains configuration options for the epoll(7) interface.
330 ----------------
336 Each "watch" costs roughly 90 bytes on a 32-bit kernel, and roughly 160 bytes
337 on a 64-bit one.
341 5. /proc/sys/fs/fuse - Configuration options for FUSE filesystems
344 This directory contains the following configuration options for FUSE