/linux/Documentation/ABI/removed/ |
H A D | sysfs-mce | 22 risk of deadlock. Higher tolerant values trade potentially 23 better uptime with the risk of a crash or even corruption
|
/linux/Documentation/core-api/irq/ |
H A D | irqflags-tracing.rst | 22 rather straightforward and risk-free manner. 46 In general there is no risk from having an incomplete irq-flags-tracing
|
/linux/tools/power/cpupower/debug/i386/ |
H A D | intel_gsic.c | 52 "RISK.\n"); in main() 59 "RISK.\n"); in main()
|
/linux/drivers/gpu/drm/etnaviv/ |
H A D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
/linux/include/linux/ |
H A D | file_ref.h | 89 * the deadzone risk end up marking someone else's file as dead in file_ref_get() 145 * calls don't risk UAFs when a file is recyclyed, it is still in file_ref_put()
|
/linux/Documentation/misc-devices/ |
H A D | ics932s401.rst | 36 do this, as you risk damaging your system!
|
/linux/Documentation/process/ |
H A D | handling-regressions.rst | 217 * In case you are unsure if a fix is worth the risk applying just days before 271 How to deal with changes where a risk of regression is known 274 Evaluate how big the risk of regressions is, for example by performing a code 280 If the risk of regressions in the end seems to be relatively small, go ahead 281 with the change, but let all involved parties know about the risk. Hence, make 284 list about the risk, so everyone has the change on the radar in case reports 285 trickle in. Depending on the risk, you also might want to ask the subsystem
|
H A D | deprecated.rst | 58 risk of them overflowing. This could lead to values wrapping around and a 127 compiler flags help reduce the risk of using this function, there is 194 eliminate VLAs, they are also a security risk. Dynamic growth of a stack
|
/linux/drivers/net/wireless/ath/carl9170/ |
H A D | Kconfig | 53 other rng source and you can afford to take the risk.
|
/linux/Documentation/usb/ |
H A D | ohci.rst | 29 transfers. Previously, using periods of one frame would risk data loss due
|
/linux/kernel/bpf/ |
H A D | mmap_unlock_work.h | 19 * risk to deadlock with rq_lock. To look up vma when the irqs are
|
/linux/arch/powerpc/platforms/pseries/ |
H A D | kexec.c | 23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
|
/linux/Documentation/filesystems/ |
H A D | hfsplus.rst | 50 or locked. Use at your own risk.
|
/linux/arch/arm64/include/asm/ |
H A D | rwonce.h | 23 * When building with LTO, there is an increased risk of the compiler
|
/linux/Documentation/dev-tools/ |
H A D | kfence.rst | 49 idle systems, at the risk of unpredictable sample intervals. The default is 295 If pool utilization reaches 75% (default) or above, to reduce the risk of the 301 filling up the pool permanently, which is the most common risk for the pool
|
/linux/Documentation/doc-guide/ |
H A D | maintainer-profile.rst | 42 window opens, since the risk of regressions from documentation patches is
|
/linux/Documentation/driver-api/md/ |
H A D | raid5-ppl.rst | 46 are not likely due to high risk of multiple disks failure. Such restriction
|
/linux/tools/testing/selftests/timers/ |
H A D | leapcrash.c | 11 * RUN AT YOUR OWN RISK!
|
/linux/drivers/gpu/drm/i915/ |
H A D | i915_utils.c | 72 * of the addition and reduce the risk of losing a jiffy. in set_timer_ms()
|
/linux/Documentation/i2c/busses/ |
H A D | i2c-sis96x.rst | 48 AND is willing to risk crashing & burning an otherwise well-behaved kernel
|
/linux/lib/ |
H A D | Kconfig.kfence | 52 CPU wake-ups if the system is idle, at the risk of a less predictable
|
/linux/arch/arm64/kernel/vdso/ |
H A D | sigreturn.S | 29 * much more comprehensive to reduce the risk of further regressions.
|
/linux/include/asm-generic/ |
H A D | delay.h | 46 * risk is given.
|
/linux/arch/x86/kernel/ |
H A D | ebda.c | 40 * too much, to not risk reserving too little.
|
/linux/Documentation/driver-api/nvdimm/ |
H A D | firmware-activate.rst | 55 assume the risk of racing firmware update with in-flight device and
|