Searched full:risk (Results 1 – 25 of 435) sorted by relevance
12345678910>>...18
| /Linux-v6.1/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-v6.1/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-v6.1/tools/power/cpupower/debug/i386/ |
| D | intel_gsic.c | 52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
|
| /Linux-v6.1/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-v6.1/drivers/virt/coco/sev-guest/ |
| D | Kconfig | 9 the PSP without risk from a malicious hypervisor who wishes to read,
|
| /Linux-v6.1/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
| /Linux-v6.1/drivers/staging/media/atomisp/pci/ |
| D | atomisp_internal.h | 110 * The bigger the value, the higher risk that the ISP is not
112 * vertical blanking time, increasing risk of dropped frames.
|
| /Linux-v6.1/mm/ |
| D | Kconfig.debug | 127 reduce the risk of information leaks from freed data. This does
170 mappings after applying NX, as such mappings are a security risk.
|
| /Linux-v6.1/Documentation/misc-devices/ |
| D | ics932s401.rst | 36 do this, as you risk damaging your system!
|
| /Linux-v6.1/drivers/net/wireless/ath/carl9170/ |
| D | Kconfig | 53 other rng source and you can afford to take the risk.
|
| /Linux-v6.1/Documentation/usb/ |
| D | ohci.rst | 29 transfers. Previously, using periods of one frame would risk data loss due
|
| /Linux-v6.1/kernel/bpf/ |
| D | mmap_unlock_work.h | 19 * risk to deadlock with rq_lock. To look up vma when the irqs are
|
| /Linux-v6.1/arch/powerpc/platforms/pseries/ |
| D | kexec.c | 23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | hfsplus.rst | 50 or locked. Use at your own risk.
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | transhuge.rst | 82 to eliminate any risk of wasting any precious byte of memory and to
86 risk to lose memory by using hugepages, should use
99 regions (to avoid the risk of consuming more memory resources) or enabled
|
| /Linux-v6.1/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 35 window opens, since the risk of regressions from documentation patches is
|
| /Linux-v6.1/arch/arm64/include/asm/ |
| D | rwonce.h | 27 * When building with LTO, there is an increased risk of the compiler
|
| /Linux-v6.1/fs/erofs/ |
| D | super.c | 422 erofs_info(sb, "EXPERIMENTAL compressed inline data feature in use. Use at your own risk!"); in erofs_read_superblock()
424 erofs_info(sb, "EXPERIMENTAL fscache-based on-demand read feature in use. Use at your own risk!"); in erofs_read_superblock()
426 erofs_info(sb, "EXPERIMENTAL compressed fragments feature in use. Use at your own risk!"); in erofs_read_superblock()
428 erofs_info(sb, "EXPERIMENTAL global deduplication feature in use. Use at your own risk!"); in erofs_read_superblock()
495 warnfc(fc, "DAX enabled. Warning: EXPERIMENTAL, use at your own risk"); in erofs_fc_set_dax_mode()
|
| /Linux-v6.1/Documentation/process/ |
| D | handling-regressions.rst | 220 How to deal with changes where a risk of regression is known
223 Evaluate how big the risk of regressions is, for example by performing a code
229 If the risk of regressions in the end seems to be relatively small, go ahead
230 with the change, but let all involved parties know about the risk. Hence, make
233 list about the risk, so everyone has the change on the radar in case reports
234 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-v6.1/include/linux/ |
| D | delay.h | 31 * risk overflow for high loops_per_jiffy (high bogomips) machines. The
|
| /Linux-v6.1/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 46 are not likely due to high risk of multiple disks failure. Such restriction
|
| /Linux-v6.1/tools/testing/selftests/timers/ |
| D | leapcrash.c | 11 * RUN AT YOUR OWN RISK!
|
| /Linux-v6.1/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-v6.1/arch/arm64/kernel/ |
| D | kaslr.c | 66 * kernel. This reduces the risk of modules leaking information in kaslr_init()
|
12345678910>>...18
