| /kernel/linux/linux-5.10/arch/arm/kernel/ |
| D | smp_tlb.c | 106 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
110 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
112 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
117 * by an active process can lead to unexpected behavior in erratum_a15_798181_init()
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | deprecated.rst | 58 risk of them overflowing. This could lead to values wrapping around and a
60 allocations could lead to linear overflows of heap memory and other
101 explicitly ignore overflows, which may lead to unexpected results
122 be NUL terminated. This can lead to various linear read overflows and
142 size limit. This is both inefficient and can lead to linear read overflows
149 Traditionally, using "%p" in format strings would lead to regular address
176 lead to a crash, possible overwriting sensitive contents at the end of the
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | compiler.h | 17 * that can lead to instructions from beyond an unreachable statement being
19 * is the only content of a case in a switch statement. This can lead to
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adm1026.rst | 96 voltage from the power lead rather than on the ground lead.
|
| /kernel/linux/linux-5.10/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /kernel/linux/linux-5.10/Documentation/ide/ |
| D | warm-plug-howto.rst | 18 results may be unpredictable and lead to data loss if you're unlucky
|
| /kernel/linux/linux-5.10/drivers/media/pci/ivtv/ |
| D | ivtvfb.c | 379 u16 lead = 0, tail = 0; in ivtvfb_write() local
414 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
415 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
417 buf += lead; in ivtvfb_write()
418 dst += lead; in ivtvfb_write()
421 if ((count - lead) & 3) in ivtvfb_write()
422 tail = (count - lead) & 3; in ivtvfb_write()
424 dma_size = count - lead - tail; in ivtvfb_write()
426 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | unaligned.h | 6 * but we don't want to use linux/unaligned/access_ok.h since that can lead
|
| /kernel/linux/linux-5.10/arch/powerpc/mm/book3s64/ |
| D | Makefile | 22 # Instrumenting the SLB fault path can lead to duplicate SLB entries
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/allwinner/ |
| D | sun50i-a64-pinephone-1.1.dts | 17 * 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
|
| D | sun50i-a64-pinephone-1.2.dts | 17 * and the lowest PWM duty cycle that doesn't lead to backlight being off
|
| /kernel/linux/linux-5.10/drivers/media/pci/ddbridge/ |
| D | Kconfig | 40 might lead to I2C errors originating from the bridge in conjunction
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | acenv.h | 22 * sleep state and cannot lead to data loss.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | i915_switcheroo.c | 42 * FIXME: open_count is protected by drm_global_mutex but that would lead to in i915_switcheroo_can_switch()
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig.hardening | 89 this with CONFIG_KASAN_STACK can lead to a stack overflow
106 this with CONFIG_KASAN_STACK can lead to a stack overflow
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/i2c/ |
| D | adv7343.txt | 3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs4234.yaml | 22 provide lead time for the external switch-mode power supply, and a
|
| /kernel/linux/linux-5.10/include/net/ |
| D | cls_cgroup.h | 59 * would lead to false results. in task_get_classid()
|
| /kernel/linux/linux-5.10/drivers/eisa/ |
| D | Kconfig | 48 # an X86 may lead to crashes...
|
| /kernel/linux/linux-5.10/arch/arm64/mm/ |
| D | mmap.c | 32 * entire range. In theory, this could lead to false negatives in valid_phys_addr_range()
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig | 913 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
951 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
957 optimisation in the Cortex-A9 Store Buffer may lead to data
1024 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
1060 lead to either a data corruption or a CPU deadlock. Not fixed in
1067 bool "ARM errata: A12: sequence of VMOV to core registers might lead to a dead lock"
1073 one is in the shadow of a branch or abort, can lead to a
1108 lead to either a data corruption or a CPU deadlock. Not fixed in
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | ftrace.h | 94 * different system call table is used for compat tasks. This may lead
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| D | Kconfig | 49 operations which can lead to the hijacking of the boot sequence are
|
| /kernel/linux/linux-5.10/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 9 disks is missing. This can lead to silent data corruption when rebuilding the
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/ibm/ehea/ |
| D | ehea_qmr.h | 145 /* Defines which bad send cqe stati lead to a port reset */
185 /* Defines which affiliated errors lead to a port reset */
|