Searched full:privilege (Results 1 – 25 of 32) sorted by relevance
12
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 13 enablement, privilege, and compatibility metadata.
94 - usable-privilege
104 This property describes the privilege levels and/or software components
118 This property describes the HV privilege support required to enable the
119 feature to lesser privilege levels. If the property does not exist then no
137 This property describes the OS privilege support required to enable the
138 feature to lesser privilege levels. If the property does not exist then no
179 This property may exist when the usable-privilege property value has PR bit set.
213 usable-privilege = <1 | 2 | 4>;
219 usable-privilege = <1 | 2>;
[all …]
|
| /Documentation/ia64/ |
| D | fsys.rst | 34 - execution is at privilege level 0 (most-privileged)
51 privilege level is at level 0, this means that fsys-mode requires some
58 Linux operates in fsys-mode when (a) the privilege level is 0 (most
70 to by "regs" was executing in user mode (privilege level 3).
177 is exited. This is accomplished with the help of the lower-privilege
181 "br.ret" instruction that lowers the privilege level, a trap will
216 breakpoint that triggers at any privilege level other than
222 syscall_via_break(), with privilege level 3. Note: the
228 taken _after_ restoring the privilege level, the CPU has already
241 syscall_via_break(), with privilege level 3.
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 26 promises not to grant the privilege to do anything that could not have
41 Note that ``no_new_privs`` does not prevent privilege changes that do not
|
| D | spec_ctrl.rst | 7 privilege domains.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | sifive,plic-1.0.0.txt | 9 A hart context is a privilege mode in a hardware execution thread. For example,
11 privilege modes per hart; machine mode and supervisor mode.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 11 privilege level of the SDEI firmware (specified as part of the binding
|
| /Documentation/driver-api/firmware/ |
| D | other_interfaces.rst | 18 Some features of the Intel Stratix10 SoC require a level of privilege
|
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 425 Privilege:
427 policy is said to have privilege. As of this writing a task can
428 have privilege either by possessing capabilities or by having an
614 only be changed by a process with privilege.
616 Privilege section in Smack Basics
779 privilege.
793 program has appropriate privilege::
798 packets will be checked if the program has appropriate privilege.
|
| D | SafeSetID.rst | 72 initial system user namespace, affectively preventing privilege escalation.
|
| /Documentation/powerpc/ |
| D | ultravisor.rst | 26 | Privilege States |
68 * The privilege of a process is now determined by three MSR bits,
70 from least privilege to highest privilege. The higher privilege
71 modes can access all the resources of the lower privilege modes.
76 | S | HV| PR|Privilege |
90 | S | HV| PR|Privilege |
|
| /Documentation/filesystems/ |
| D | overlayfs.txt | 117 caller without certain key capabilities or lower privilege will not
122 caller can fill cache, then a lower privilege can read the directory
124 are opened at privilege, but accessed without creating a form of
125 privilege escalation, should only be used with strict understanding
|
| D | fuse.txt | 299 privilege to send signal to the process accessing the
|
| /Documentation/admin-guide/ |
| D | security-bugs.rst | 62 Fixes for sensitive bugs, such as those that might lead to privilege
|
| /Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 21 Functions are invoked by trapping to the privilege level of the PSCI
|
| /Documentation/parisc/ |
| D | registers.rst | 70 H (Higher-privilege trap) 0
71 L (Lower-privilege trap) 0
|
| /Documentation/admin-guide/sysctl/ |
| D | fs.rst | 225 is to cross privilege boundaries when following a given hardlink (i.e. a
261 is to cross privilege boundaries when following a given symlink (i.e. a
283 privilege levels or is execute only will not be dumped.
|
| /Documentation/devicetree/bindings/c6x/ |
| D | dscr.txt | 97 Offset and default value for register used to set access privilege for
|
| /Documentation/security/ |
| D | credentials.rst | 238 * UNIX exec privilege escalation bits (SUID/SGID);
239 * File capabilities exec privilege escalation bits.
243 privilege escalation bits come into play, and may allow the resulting process
|
| /Documentation/virt/kvm/devices/ |
| D | xive.txt | 34 a view with a different privilege. The first page is for the
|
| /Documentation/ |
| D | DMA-attributes.txt | 156 subsystem that the buffer is fully accessible at the elevated privilege
|
| /Documentation/x86/ |
| D | intel_txt.rst | 223 because it operates at a higher privilege level in the system than
|
| /Documentation/riscv/ |
| D | pmu.rst | 79 (2) privilege level setting (user space only, kernel space only, both);
|
| /Documentation/admin-guide/hw-vuln/ |
| D | tsx_async_abort.rst | 81 privilege escalation by using this technique.
|
| /Documentation/admin-guide/mm/ |
| D | hugetlbpage.rst | 88 pool, a user with appropriate privilege can use either the mmap system call
|
| /Documentation/arm64/ |
| D | acpi_object_usage.rst | 666 interrupts at higher privilege levels or even interrupts at the same priority
|
12