Searched full:risk (Results 1 – 25 of 397) sorted by relevance
12345678910>>...16
| /linux-5.10/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-5.10/tools/power/cpupower/debug/i386/ |
| D | intel_gsic.c | 52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
|
| /linux-5.10/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 56 how hard the kernel tries to recover even at some risk of
58 with the risk of a crash or even corruption (for tolerant >= 3).
|
| /linux-5.10/include/trace/events/ |
| D | rcu.h | 663 * and the sixth argument (risk) is the return value from
669 char cb, char nr, char iit, char risk),
671 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk),
679 __field(char, risk)
688 __entry->risk = risk;
696 __entry->risk ? 'R' : '.')
|
| /linux-5.10/mm/ |
| D | Kconfig.debug | 71 reduce the risk of information leaks from freed data. This does
133 mappings after applying NX, as such mappings are a security risk.
|
| /linux-5.10/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
| /linux-5.10/Documentation/misc-devices/ |
| D | ics932s401.rst | 36 do this, as you risk damaging your system!
|
| /linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | atomisp_internal.h | 115 * The bigger the value, the higher risk that the ISP is not
117 * vertical blanking time, increasing risk of dropped frames.
|
| /linux-5.10/drivers/net/wireless/ath/carl9170/ |
| D | Kconfig | 55 other rng source and you can afford to take the risk.
|
| /linux-5.10/Documentation/usb/ |
| D | ohci.rst | 29 transfers. Previously, using periods of one frame would risk data loss due
|
| /linux-5.10/arch/powerpc/platforms/pseries/ |
| D | kexec.c | 23 * Don't risk a hypervisor call if we're crashing in pseries_kexec_cpu_down()
|
| /linux-5.10/Documentation/filesystems/ |
| D | hfsplus.rst | 50 or locked. Use at your own risk.
|
| /linux-5.10/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 35 window opens, since the risk of regressions from documentation patches is
|
| /linux-5.10/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-5.10/include/linux/ |
| D | delay.h | 30 * risk overflow for high loops_per_jiffy (high bogomips) machines. The
|
| /linux-5.10/Documentation/process/ |
| D | deprecated.rst | 58 risk of them overflowing. This could lead to values wrapping around and a
112 compiler flags help reduce the risk of using this function, there is
174 eliminate VLAs, they are also a security risk. Dynamic growth of a stack
|
| /linux-5.10/tools/testing/selftests/timers/ |
| D | leapcrash.c | 11 * RUN AT YOUR OWN RISK!
|
| /linux-5.10/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 46 are not likely due to high risk of multiple disks failure. Such restriction
|
| /linux-5.10/arch/arm64/kernel/vdso/ |
| D | sigreturn.S | 29 * much more comprehensive to reduce the risk of further regressions.
|
| /linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_utils.c | 110 * of the addition and reduce the risk of losing a jiffie. in set_timer_ms()
|
| /linux-5.10/Documentation/i2c/busses/ |
| D | i2c-sis96x.rst | 48 AND is willing to risk crashing & burning an otherwise well-behaved kernel
|
| /linux-5.10/drivers/crypto/cavium/zip/ |
| D | zip_deflate.h | 42 * ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE LIES
|
| D | zip_inflate.h | 42 * ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE LIES
|
| /linux-5.10/arch/x86/kernel/ |
| D | ebda.c | 40 * too much, to not risk reserving too little.
|
| /linux-5.10/include/uapi/linux/ |
| D | sem.h | 75 * risk that semop()/semtimedop() fails due to kernel memory fragmentation when
|
12345678910>>...16