Home
last modified time | relevance | path

Searched full:risk (Results 1 – 25 of 338) sorted by relevance

12345678910>>...14

/linux/Documentation/ABI/removed/
H A Dsysfs-mce22 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 Dirqflags-tracing.rst22 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 Dintel_gsic.c52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
/linux/drivers/gpu/drm/etnaviv/
H A DKconfig24 Say Y unless you want to risk burning your SoC.
/linux/include/linux/
H A Dfile_ref.h89 * 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()
H A Dtracefs.h60 * the tracefs or eventfs system or it will risk creating a deadlock.
/linux/Documentation/misc-devices/
H A Dics932s401.rst36 do this, as you risk damaging your system!
/linux/drivers/net/wireless/ath/carl9170/
H A DKconfig53 other rng source and you can afford to take the risk.
/linux/Documentation/usb/
H A Dohci.rst29 transfers. Previously, using periods of one frame would risk data loss due
/linux/kernel/bpf/
H A Dmmap_unlock_work.h19 * risk to deadlock with rq_lock. To look up vma when the irqs are
/linux/arch/powerpc/platforms/pseries/
H A Dkexec.c23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
/linux/Documentation/filesystems/
H A Dhfsplus.rst50 or locked. Use at your own risk.
/linux/Documentation/doc-guide/
H A Dmaintainer-profile.rst42 window opens, since the risk of regressions from documentation patches is
/linux/Documentation/process/
H A Dthreat-model.rst86 are designed to be accessible to regular local users with a low risk (e.g.
88 represent a risk in most places and the decision to expose them is under the
/linux/Documentation/driver-api/md/
H A Draid5-ppl.rst46 are not likely due to high risk of multiple disks failure. Such restriction
/linux/tools/testing/selftests/timers/
H A Dleapcrash.c11 * RUN AT YOUR OWN RISK!
/linux/Documentation/i2c/busses/
H A Di2c-sis96x.rst48 AND is willing to risk crashing & burning an otherwise well-behaved kernel
/linux/lib/
H A DKconfig.kfence52 CPU wake-ups if the system is idle, at the risk of a less predictable
/linux/arch/arm64/kernel/vdso/
H A Dsigreturn.S29 * much more comprehensive to reduce the risk of further regressions.
/linux/include/asm-generic/
H A Ddelay.h46 * risk is given.
/linux/arch/x86/kernel/
H A Debda.c40 * too much, to not risk reserving too little.
/linux/Documentation/driver-api/nvdimm/
H A Dfirmware-activate.rst55 assume the risk of racing firmware update with in-flight device and
/linux/include/uapi/linux/
H A Dsem.h75 * risk that semop()/semtimedop() fails due to kernel memory fragmentation when
/linux/Documentation/i2c/
H A Ddma-considerations.rst27 updated to use this flag will work like before. And like before, they risk
/linux/Documentation/arch/powerpc/
H A Ddawr-power9.rst76 This is a dangerous setting, USE AT YOUR OWN RISK.

12345678910>>...14