| /linux-6.12.1/arch/arm/mm/ |
| D | proc-sa110.S | 98 mov r0, r0 @ safety
99 mov r0, r0 @ safety
100 mov r0, r0 @ safety
102 mov r0, r0 @ safety
103 mov r0, r0 @ safety
104 mov r0, r0 @ safety
|
| D | proc-sa1100.S | 114 mov r0, r0 @ safety
|
| /linux-6.12.1/Documentation/translations/zh_CN/rust/ |
| D | coding-guidelines.rst | 85 // SAFETY: `p` is valid by the safety requirements.
127 // SAFETY: The safety contract must be upheld by the caller.
|
| /linux-6.12.1/arch/x86/include/asm/ |
| D | suspend_32.h | 23 unsigned long safety; member
|
| D | suspend_64.h | 52 unsigned long safety; member
|
| /linux-6.12.1/arch/powerpc/boot/dts/ |
| D | ac14xx.dts | 45 0x5 0x0 0xe0400000 0x00010000 /* CS5: safety */
125 safety@5,0 {
126 compatible = "ifm,safety";
|
| /linux-6.12.1/Documentation/rust/ |
| D | general-information.rst | 110 #. Any ``unsafe`` blocks respect the safety contract necessary to call the
112 safety contract necessary to implement the trait.
136 Besides the safety aspect, the abstractions are supposed to be "ergonomic", in
|
| D | coding-guidelines.rst | 94 // SAFETY: `p` is valid by the safety requirements.
140 // SAFETY: The safety contract must be upheld by the caller.
151 - Unsafe functions must document their safety preconditions under
|
| /linux-6.12.1/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 19 CPU/SOC, for thermal safety reasons.
|
| /linux-6.12.1/net/hsr/ |
| D | Kconfig | 38 relying on this code in a safety critical system!
|
| /linux-6.12.1/drivers/media/pci/saa7164/ |
| D | saa7164-cmd.c | 336 int safety = 0; in saa7164_cmd_send() local
444 if (safety++ > 16) { in saa7164_cmd_send()
|
| /linux-6.12.1/lib/ |
| D | Kconfig.kasan | 35 bool "KASAN: dynamic memory safety error detector"
43 Enables KASAN (Kernel Address Sanitizer) - a dynamic memory safety
|
| D | Kconfig.kfence | 7 bool "KFENCE: low-overhead sampling-based memory safety error detector"
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | index.rst | 63 Linux kernel for safety critical applications. Documents supporting
|
| /linux-6.12.1/arch/arm/boot/dts/arm/ |
| D | arm-realview-eb-mp.dtsi | 74 * up by boot loader(s), probably for safety
|
| /linux-6.12.1/Documentation/driver-api/driver-model/ |
| D | bus.rst | 53 type-safety.
|
| /linux-6.12.1/drivers/net/wan/ |
| D | farsync.c | 911 int safety; in fst_issue_cmd() local
917 safety = 0; in fst_issue_cmd()
924 if (++safety > 2000) { in fst_issue_cmd()
931 if (safety > 0) in fst_issue_cmd()
932 dbg(DBG_CMD, "Mailbox clear after %d jiffies\n", safety); in fst_issue_cmd()
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | ocfs2.rst | 83 will hurt performance, but it's good for data-safety.
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | interconnect.rst | 118 any arbitrary path. Note that for safety reasons, this feature is disabled by
|
| /linux-6.12.1/Documentation/i2c/busses/ |
| D | i2c-parport.rst | 94 the i2c-parport module might be a good safety since data line state
|
| /linux-6.12.1/drivers/cxl/ |
| D | Kconfig | 143 can disable that data integrity safety and proceed with enabling
|
| /linux-6.12.1/Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 83 Without the option META_BG, for safety concerns, all block group
|
| /linux-6.12.1/tools/net/sunrpc/xdrgen/ |
| D | README | 16 network, and thus a high degree of memory safety and sanity checking
|
| /linux-6.12.1/Documentation/trace/rv/ |
| D | runtime-verification.rst | 20 events, avoiding, for example, the propagation of a failure on safety-critical
|
| /linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 151 To ensure the safety of this mitigation, the kernel must ensure that the
|