Lines Matching +full:files +full:- +full:based
11 ------------------------------------------------------------------------------
13 This file contains documentation for the sysctl files and directories
16 The files in this directory can be used to tune and monitor
18 kernel. Since some of the files *can* be used to screw up your
25 Currently, these files might (depending on your configuration)
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.
42 dentry-state
43 ------------
69 negative dentries which do not map to any files. Instead,
70 they help speeding up rejection of non-existing files provided
74 file-max & file-nr
75 ------------------
77 The value in ``file-max`` denotes the maximum number of file-
84 ``file-nr`` denote the number of allocated file handles, the number
87 file handles -- this is not an error, it just means that the
91 Attempts to allocate more file descriptors than ``file-max`` are
94 VFS: file-max limit <number> reached
99 inode-nr & inode-state
100 ----------------------
105 The file ``inode-nr`` contains the first two items from
106 ``inode-state``, so we'll skip to that file...
108 ``inode-state`` contains three actual numbers and four dummies.
121 mount-max
122 ---------
129 -------
131 This denotes the maximum number of file-handles a process can
138 -------------------------
140 Some filesystems only support 16-bit UIDs and GIDs, although in Linux
149 pipe-user-pages-hard
150 --------------------
152 Maximum total number of pages a non-privileged user may allocate for pipes.
158 pipe-user-pages-soft
159 --------------------
161 Maximum total number of pages a non-privileged user may allocate for pipes
171 ---------------
174 an attacker-controlled FIFO, where a program expected to create a regular
185 This protection is based on the restrictions in Openwall.
189 --------------------
191 A long-standing class of security issues is the hardlink-based
192 time-of-check-time-of-use race, most commonly seen in world-writable
197 from "pinning" vulnerable setuid/setgid files against being upgraded by
198 the administrator, or linking to special files.
205 This protection is based on the restrictions in Openwall and grsecurity.
209 -----------------
212 avoids writes to an attacker-controlled regular file, where a program
215 When set to "0", writing to regular files is unrestricted.
217 When set to "1" don't allow ``O_CREAT`` open on regular files that we
225 ------------------
227 A long-standing class of security issues is the symlink-based
228 time-of-check-time-of-use race, most commonly seen in world-writable
233 https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=/tmp
238 a sticky world-writable directory, or when the uid of the symlink and
241 This protection is based on the restrictions in Openwall and grsecurity.
245 -------------
261 :ref:`Documentation/admin-guide/sysctl/kernel.rst <core_pattern>`)
264 details on this limitation, see CVE-2006-2451.) This mode is
279 Documentation for the files in ``/proc/sys/fs/binfmt_misc`` is
280 in Documentation/admin-guide/binfmt-misc.rst.
283 3. /proc/sys/fs/mqueue - POSIX message queues filesystem
289 API (as noted by the MSG tag in the POSIX 1003.1-2001 version of the System
319 4. /proc/sys/fs/epoll - Configuration options for the epoll interface
325 ----------------
327 Every epoll file descriptor can store a number of files to be monitored
328 for event readiness. Each one of these monitored files constitutes a "watch".
331 Each "watch" costs roughly 90 bytes on a 32-bit kernel, and roughly 160 bytes
332 on a 64-bit one.