Searched full:executable (Results 1 – 25 of 57) sorted by relevance
123
| /Documentation/userspace-api/ |
| D | mfd_noexec.rst | 4 Introduction of non-executable mfd
19 boot), this executable nature of memfd opens a door for NoExec bypass
25 On the other hand, executable memfd has its legit use: runc uses memfd’s
26 seal and executable feature to copy the contents of the binary then
28 use of executable memfds and an attacker's [3].
34 migrating and enforcing non-executable MFD.
72 doesn't set the executable bit; for example, a container with
73 vm.memfd_noexec=1 means the old software will create non-executable memfd
74 by default while new software can create executable memfd by setting
|
| D | ELF.rst | 33 program header of an executable is used. Other PT_GNU_PROPERTY headers
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 108 non-executable pages. This forces all iTLB entries to be 4K, and removes
112 as non-executable. If the guest attempts to execute in one of those pages,
113 the page is broken down into 4K pages, which are then marked executable.
120 non-executable in all shadow paging modes.
126 non-executable can be controlled with a module parameter "nx_huge_pages=".
134 non-executable huge pages in Linux kernel KVM module. All huge
135 pages in the EPT are marked as non-executable.
137 broken down into 4K pages, which are then marked executable.
|
| /Documentation/translations/zh_CN/arch/riscv/ |
| D | boot-image-header.rst | 25 u32 code0; /* Executable code */
26 u32 code1; /* Executable code */
|
| /Documentation/arch/riscv/ |
| D | boot-image-header.rst | 12 u32 code0; /* Executable code */
13 u32 code1; /* Executable code */
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 112 group to Perf tool executable and limit access to the executable for
127 2. Assign the required capabilities to the Perf tool executable file and
162 configured Perf tool executable that, when executes, passes perf_events
165 In case Perf tool executable can't be assigned required capabilities (e.g.
305 executable with CAP_IPC_LOCK capability.
|
| D | java.rst | 35 support for executable Jar files::
399 Set the executable permissions of the binary file, with::
423 added executable Jar file support by Kurt Huwig <kurt@iku-netz.de>
|
| D | initrd.rst | 35 5) /sbin/init is executed (this can be any valid executable, including
119 needed to execute programs from initrd (e.g. executable format and file
240 executable, shared libraries, standard input/output/error, and its
|
| D | efi-stub.rst | 7 it as an EFI executable. The code that modifies the bzImage header,
|
| /Documentation/ABI/removed/ |
| D | sysfs-selinux-checkreqprot | 15 1, it weakens security by allowing mappings to be made executable
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 14 device executable binary (e.g. a kernel) as it's what the CFE bootloader starts
|
| /Documentation/security/ |
| D | self-protection.rst | 47 Executable code and read-only data must not be writable
50 Any areas of the kernel with executable memory must not be writable.
61 writable, data is not executable, and read-only data is neither writable
62 nor executable.
212 Blinding literal values for things like JITs, where the executable
|
| /Documentation/filesystems/ |
| D | romfs.rst | 113 the file; while bit 4 shows if the file is executable or not. The
115 and world executable if it is; except the character and block devices,
139 using the executable bits for special purposes on the socket and fifo
|
| D | hfs.rst | 57 * You can't modify the set-uid, set-gid, sticky or executable bits or the uid
|
| /Documentation/kbuild/ |
| D | makefiles.rst | 714 Two steps are required in order to use a host executable.
719 The second step is to add an explicit dependency to the executable.
747 $(<executable>-objs) lists all objects used to link the final
748 executable.
760 Finally, the two .o files are linked to the executable, lxdialog.
761 Note: The syntax <executable>-y is not permitted for host-programs.
776 In the example above the executable is composed of the C++ file
909 $(<executable>-objs) lists all objects used to link the final
910 executable.
922 Finally, the two .o files are linked to the executable, bpf-fancy.
[all …]
|
| /Documentation/trace/ |
| D | uprobetracer.rst | 37 PATH : Path to an executable or a library.
88 as below (sets a uprobe at an offset of 0x4245c0 in the executable /bin/bash)::
|
| /Documentation/fb/ |
| D | uvesafb.rst | 129 v86d:path Set path to the v86d executable. This option is only available as
157 Path to the v86d executable. v86d is started by uvesafb
|
| /Documentation/bpf/ |
| D | bpf_licensing.rst | 92 separate executable processes. This applies to both cBPF and eBPF programs.
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 70 large executable or archive). It should be at least 5 megabytes, but
|
| /Documentation/arch/arm/ |
| D | uefi.rst | 34 PE/COFF executable, including a loader application that makes it possible to
|
| /Documentation/arch/x86/ |
| D | exception-tables.rst | 59 to executable code. This code is hidden inside the user access macros.
190 final kernel executable::
208 of the executable file::
|
| /Documentation/staging/ |
| D | xz.rst | 13 for executable code. CRC32 is supported for integrity checking.
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 213 assumed to be readable and writable, not executable, and only shareable
242 controlling the device. Remember especially: private executable
|
| /Documentation/ABI/testing/ |
| D | ima_policy | 122 all files mmapped executable in file_mmap, and all files
|
| /Documentation/core-api/ |
| D | cachetlb.rst | 80 executable (and thus could be in the 'instruction TLB' in
186 executable (and thus could be in the 'instruction cache' in
|
123