Searched full:risk (Results 1 – 25 of 470) sorted by relevance
12345678910>>...19
/linux-6.8/Documentation/ABI/removed/ |
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-6.8/Documentation/core-api/irq/ |
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-6.8/tools/power/cpupower/debug/i386/ |
D | intel_gsic.c | 52 "RISK.\n"); in main() 59 "RISK.\n"); in main()
|
/linux-6.8/include/trace/events/ |
D | rcu.h | 718 * and the sixth argument (risk) is the return value from 724 char cb, char nr, char iit, char risk), 726 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk), 734 __field(char, risk) 743 __entry->risk = risk; 751 __entry->risk ? 'R' : '.')
|
/linux-6.8/drivers/staging/media/atomisp/pci/ |
D | atomisp_internal.h | 102 * The bigger the value, the higher risk that the ISP is not 104 * vertical blanking time, increasing risk of dropped frames.
|
/linux-6.8/drivers/gpu/drm/etnaviv/ |
D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
/linux-6.8/drivers/virt/coco/sev-guest/ |
D | Kconfig | 11 the PSP without risk from a malicious hypervisor who wishes to read,
|
/linux-6.8/Documentation/misc-devices/ |
D | ics932s401.rst | 36 do this, as you risk damaging your system!
|
/linux-6.8/drivers/net/wireless/ath/carl9170/ |
D | Kconfig | 53 other rng source and you can afford to take the risk.
|
/linux-6.8/Documentation/usb/ |
D | ohci.rst | 29 transfers. Previously, using periods of one frame would risk data loss due
|
/linux-6.8/kernel/bpf/ |
D | mmap_unlock_work.h | 19 * risk to deadlock with rq_lock. To look up vma when the irqs are
|
/linux-6.8/Documentation/process/ |
D | handling-regressions.rst | 210 * In case you are unsure if a fix is worth the risk applying just days before 264 How to deal with changes where a risk of regression is known 267 Evaluate how big the risk of regressions is, for example by performing a code 273 If the risk of regressions in the end seems to be relatively small, go ahead 274 with the change, but let all involved parties know about the risk. Hence, make 277 list about the risk, so everyone has the change on the radar in case reports 278 trickle in. Depending on the risk, you also might want to ask the subsystem
|
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-6.8/mm/ |
D | Kconfig.debug | 120 reduce the risk of information leaks from freed data. This does 163 mappings after applying NX, as such mappings are a security risk.
|
/linux-6.8/arch/powerpc/platforms/pseries/ |
D | kexec.c | 23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
|
/linux-6.8/Documentation/filesystems/ |
D | hfsplus.rst | 50 or locked. Use at your own risk.
|
/linux-6.8/Documentation/doc-guide/ |
D | maintainer-profile.rst | 35 window opens, since the risk of regressions from documentation patches is
|
/linux-6.8/arch/arm64/include/asm/ |
D | rwonce.h | 27 * When building with LTO, there is an increased risk of the compiler
|
/linux-6.8/tools/testing/selftests/timers/ |
D | leapcrash.c | 11 * RUN AT YOUR OWN RISK!
|
/linux-6.8/Documentation/driver-api/md/ |
D | raid5-ppl.rst | 46 are not likely due to high risk of multiple disks failure. Such restriction
|
/linux-6.8/include/linux/ |
D | delay.h | 31 * risk overflow for high loops_per_jiffy (high bogomips) machines. The
|
/linux-6.8/Documentation/dev-tools/ |
D | kfence.rst | 49 idle systems, at the risk of unpredictable sample intervals. The default is 288 If pool utilization reaches 75% (default) or above, to reduce the risk of the 294 filling up the pool permanently, which is the most common risk for the pool
|
/linux-6.8/Documentation/admin-guide/mm/ |
D | transhuge.rst | 95 to eliminate any risk of wasting any precious byte of memory and to 99 risk to lose memory by using hugepages, should use 112 regions (to avoid the risk of consuming more memory resources) or enabled
|
/linux-6.8/lib/ |
D | Kconfig.kfence | 52 CPU wake-ups if the system is idle, at the risk of a less predictable
|
/linux-6.8/arch/arm64/kernel/vdso/ |
D | sigreturn.S | 29 * much more comprehensive to reduce the risk of further regressions.
|
12345678910>>...19