| /linux/drivers/mtd/spi-nor/ |
| H A D | Kconfig | 28 prompt "Software write protection at boot"
34 This option disables the software write protection on any SPI
37 Depending on the flash chip this either clears the block protection
40 Don't use this if you intent to use the software write protection
44 bool "Disable SWP on flashes w/ volatile protection bits"
46 Some SPI flashes have volatile block protection bits, ie. after a
50 This option disables the software write protection for these kind
52 which have non-volatile write protection bits.
54 If the software write protection will be disabled depending on
55 the flash either the block protection bits are cleared or a
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-docg3 | 6 Show whether the floor (0 to 4), protection area (0 or 1) is
7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
9 The protection has information embedded whether it blocks reads,
23 Enter the protection key for the floor (0 to 4), protection area
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
26 The protection has information embedded whether it blocks reads,
28 The protection key is a string of 8 bytes (value 0-255).
|
| /linux/tools/testing/selftests/cgroup/ |
| H A D | memcg_protection.m | 5 % This script simulates reclaim protection behavior on a single level of memcg
6 % hierarchy to illustrate how overcommitted protection spreads among siblings
15 % E number parent effective protection
16 % n vector nominal protection of siblings set at the given level (memory.low)
54 % recursive protection
65 % commit 1bc63fb1272b ("mm, memcg: make scan aggression always exclude protection")
|
| /linux/Documentation/core-api/ |
| H A D | protection-keys.rst | 9 application changes protection domains.
20 a "protection key", giving 16 possible keys.
37 Pkeys use 3 bits in each page table entry, to encode a "protection key index",
42 overlay permissions for each protection key index.
47 Unlike x86_64, the protection key permissions also apply to instruction
92 The kernel attempts to make protection keys consistent with the
98 you can expect the same effects with protection keys when doing this::
115 to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
119 value for the protection key register and so will not be consistent with
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 16 protocols (SBC Data Integrity Field, SCC protection proposal) as well
19 metadata (or protection information in SCSI terminology) includes a
22 for some protection schemes also that the I/O is written to the right
29 DIF and the other integrity extensions is that the protection format
42 the protection information to be transferred to and from their
45 The SCSI Data Integrity Field works by appending 8 bytes of protection
85 The data integrity framework in Linux enables protection information
92 disadvantage. It means that the protection information must be in a
101 protection information to send to a disk. Consequently, the very
102 concept of an end-to-end protection scheme is a layering violation.
[all …]
|
| /linux/arch/arm/boot/dts/st/ |
| H A D | stm32mp15xx-osd32.dtsi | 85 regulator-over-current-protection;
94 regulator-over-current-protection;
104 regulator-over-current-protection;
112 regulator-over-current-protection;
135 regulator-over-current-protection;
|
| H A D | stm32mp15xx-dhcor-som.dtsi | 108 regulator-over-current-protection;
117 regulator-over-current-protection;
126 regulator-over-current-protection;
134 regulator-over-current-protection;
157 regulator-over-current-protection;
|
| H A D | stm32mp157c-odyssey-som.dtsi | 109 regulator-over-current-protection;
118 regulator-over-current-protection;
128 regulator-over-current-protection;
136 regulator-over-current-protection;
161 regulator-over-current-protection;
|
| H A D | stm32mp157a-stinger96.dtsi | 130 regulator-over-current-protection;
139 regulator-over-current-protection;
149 regulator-over-current-protection;
157 regulator-over-current-protection;
182 regulator-over-current-protection;
|
| H A D | stm32mp13xx-dhcor-som.dtsi | 92 regulator-over-current-protection;
101 regulator-over-current-protection;
110 regulator-over-current-protection;
119 regulator-over-current-protection;
|
| H A D | stm32mp157c-emstamp-argon.dtsi | 231 regulator-over-current-protection;
240 regulator-over-current-protection;
250 regulator-over-current-protection;
258 regulator-over-current-protection;
283 regulator-over-current-protection;
|
| /linux/arch/arm64/ |
| H A D | Makefile | 79 KBUILD_CFLAGS += -mbranch-protection=pac-ret+bti
80 KBUILD_RUSTFLAGS += -Zbranch-protection=bti,pac-ret
82 KBUILD_RUSTFLAGS += -Zbranch-protection=pac-ret
84 KBUILD_CFLAGS += -mbranch-protection=pac-ret
89 KBUILD_CFLAGS += $(call cc-option,-mbranch-protection=none)
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | pxa-usb.txt | 18 - "marvell,no-oc-protection" - disable over-current protection.
19 - "marvell,oc-mode-perport" - enable per-port over-current protection.
|
| /linux/Documentation/ABI/removed/ |
| H A D | sysfs-selinux-checkreqprot | 11 to check the protection requested by userspace for mmap/mprotect
12 calls instead of the actual protection applied by the kernel.
18 actual protection), and Android and Linux distributions have been
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | disk-shock-protection.rst | 2 Hard disk shock protection
25 a shock protection facility. The idea is to stop all I/O operations on
31 system in order to get disk shock protection working (see
128 protection capabilities. As manufacturers have refused to support open
130 support for shock protection varies considerably between different
133 protection on different systems. Unfortunately, I only know of a
141 active protection system as implemented in IBM/Lenovo Thinkpads.
|
| /linux/tools/testing/selftests/arm64/bti/ |
| H A D | Makefile | 11 CFLAGS_NOBTI = -mbranch-protection=none -DBTI=0
12 CFLAGS_BTI = -mbranch-protection=standard -DBTI=1
|
| /linux/drivers/irqchip/ |
| H A D | irq-omap-intc.c | 59 u32 protection; member
88 intc_context.protection = in omap_intc_save_context()
108 intc_writel(INTC_PROTECTION, intc_context.protection); in omap_intc_restore_context()
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | vmscape.rst | 56 vulnerable to cross-thread attacks. For complete protection against VMSCAPE
60 protection. Warning is not issued when:
64 - Intel eIBRS is enabled (which implies STIBP protection)
|
| H A D | l1tf.rst | 58 While Meltdown breaks the user space to kernel space protection, L1TF
60 works across all protection domains. It allows an attack of SGX and also
62 extended page table (EPT) protection mechanism.
111 deployment scenario. The mitigations, their protection scope and impact
132 'Mitigation: PTE Inversion' The host protection is active
155 The resulting grade of protection is discussed in the following sections.
198 maximum protection. It has a higher overhead than the conditional
501 L1D flushing on VMENTER is the minimal protection requirement, but it
526 The above three mitigation methods combined can provide protection to a
528 carefully analyzed. For full protection the following methods are
[all …]
|
| /linux/Documentation/arch/x86/ |
| H A D | intel_txt.rst | 14 - Data protection in case of improper shutdown
78 protection, memory configuration/alias checks and locks, crash
79 protection, or policy support.
84 protection is provided to all launched components, a large number
86 protection is provided for any data in the event of an improper
142 in order to remove this blanket protection and use VT-d's
143 page-level protection.
|
| /linux/Documentation/translations/zh_CN/ |
| H A D | how-to.rst | 254 docs/zh_CN: Add self-protection index Chinese translation
256 Translate .../security/self-protection.rst into Chinese.
259 ("docs: update self-protection __ro_after_init status")
|
| /linux/drivers/video/fbdev/omap2/omapfb/displays/ |
| H A D | Kconfig | 17 tristate "TPD12S015 HDMI ESD protection and level shifter"
19 Driver for TPD12S015, which offers HDMI ESD protection and level
|
| /linux/fs/verity/ |
| H A D | Kconfig | 4 bool "FS Verity (read-only file-based authenticity protection)"
30 protection against malicious disks vs. an ahead-of-time hash.
|
| /linux/Documentation/security/ |
| H A D | index.rst | 16 self-protection
|
| H A D | digsig.rst | 20 Currently digital signatures are used by the IMA/EVM integrity protection subsystem.
51 protection.
|