Searched full:risk (Results 1 – 25 of 498) sorted by relevance
12345678910>>...20
| /linux-6.14.4/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.14.4/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.14.4/tools/power/cpupower/debug/i386/ |
| D | intel_gsic.c | 52 "RISK.\n"); in main()
59 "RISK.\n"); in main()
|
| /linux-6.14.4/include/trace/events/ |
| D | rcu.h | 745 * and the sixth argument (risk) is the return value from
751 char cb, char nr, char iit, char risk),
753 TP_ARGS(rcuname, callbacks_invoked, cb, nr, iit, risk),
761 __field(char, risk)
770 __entry->risk = risk;
778 __entry->risk ? 'R' : '.')
|
| /linux-6.14.4/drivers/staging/media/atomisp/pci/ |
| D | atomisp_internal.h | 89 * The bigger the value, the higher risk that the ISP is not
91 * vertical blanking time, increasing risk of dropped frames.
|
| /linux-6.14.4/drivers/virt/coco/sev-guest/ |
| D | Kconfig | 8 the PSP without risk from a malicious hypervisor who wishes to read,
|
| /linux-6.14.4/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 24 Say Y unless you want to risk burning your SoC.
|
| /linux-6.14.4/include/linux/ |
| 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-6.14.4/drivers/power/sequencing/ |
| D | Kconfig | 27 this driver is needed for correct power control or else we'd risk not
|
| /linux-6.14.4/Documentation/misc-devices/ |
| D | ics932s401.rst | 36 do this, as you risk damaging your system!
|
| /linux-6.14.4/drivers/net/wireless/ath/carl9170/ |
| D | Kconfig | 53 other rng source and you can afford to take the risk.
|
| /linux-6.14.4/Documentation/usb/ |
| D | ohci.rst | 29 transfers. Previously, using periods of one frame would risk data loss due
|
| /linux-6.14.4/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.14.4/kernel/bpf/ |
| D | mmap_unlock_work.h | 19 * risk to deadlock with rq_lock. To look up vma when the irqs are
|
| /linux-6.14.4/Documentation/process/ |
| 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
|
| 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.14.4/Documentation/filesystems/ |
| D | hfsplus.rst | 50 or locked. Use at your own risk.
|
| /linux-6.14.4/mm/ |
| D | Kconfig.debug | 152 reduce the risk of information leaks from freed data. This does
195 mappings after applying NX, as such mappings are a security risk.
|
| /linux-6.14.4/arch/arm64/include/asm/ |
| D | rwonce.h | 27 * When building with LTO, there is an increased risk of the compiler
|
| /linux-6.14.4/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 42 window opens, since the risk of regressions from documentation patches is
|
| /linux-6.14.4/drivers/gpu/drm/i915/ |
| D | i915_utils.c | 72 * of the addition and reduce the risk of losing a jiffy. in set_timer_ms()
|
| /linux-6.14.4/drivers/firmware/efi/libstub/ |
| D | pci.c | 51 * Don't disconnect VGA controllers so we don't risk losing in efi_pci_disable_bridge_busmaster()
|
| /linux-6.14.4/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 46 are not likely due to high risk of multiple disks failure. Such restriction
|
| /linux-6.14.4/tools/testing/selftests/timers/ |
| D | leapcrash.c | 11 * RUN AT YOUR OWN RISK!
|
| /linux-6.14.4/Documentation/dev-tools/ |
| 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
|
12345678910>>...20