Home
last modified time | relevance | path

Searched full:lead (Results 1 – 25 of 551) sorted by relevance

12345678910>>...23

/kernel/linux/linux-5.10/arch/arm/kernel/
Dsmp_tlb.c106 * 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/
Ddeprecated.rst58 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
D7.AdvancedTopics.rst79 Excessive use of this capability can lead to other problems, though, beyond
177 All types of review, if they lead to better code going into the kernel, are
/kernel/linux/linux-5.10/arch/mips/include/asm/
Dcompiler.h17 * 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/
Dadm1026.rst96 voltage from the power lead rather than on the ground lead.
/kernel/linux/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/kernel/linux/linux-5.10/drivers/media/pci/ivtv/
Divtvfb.c379 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/Documentation/ide/
Dwarm-plug-howto.rst18 results may be unpredictable and lead to data loss if you're unlucky
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dunaligned.h6 * 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/
DMakefile22 # Instrumenting the SLB fault path can lead to duplicate SLB entries
/kernel/linux/linux-5.10/arch/arm64/boot/dts/allwinner/
Dsun50i-a64-pinephone-1.1.dts17 * 1.0, and the lowest PWM duty cycle that doesn't lead to backlight
Dsun50i-a64-pinephone-1.2.dts17 * and the lowest PWM duty cycle that doesn't lead to backlight being off
/kernel/linux/linux-5.10/drivers/media/pci/ddbridge/
DKconfig40 might lead to I2C errors originating from the bridge in conjunction
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/
Di915_switcheroo.c42 * FIXME: open_count is protected by drm_global_mutex but that would lead to in i915_switcheroo_can_switch()
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/i2c/
Dadv7343.txt3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
/kernel/linux/linux-5.10/drivers/eisa/
DKconfig48 # an X86 may lead to crashes...
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dcirrus,cs4234.yaml22 provide lead time for the external switch-mode power supply, and a
/kernel/linux/linux-5.10/include/net/
Dcls_cgroup.h59 * would lead to false results. in task_get_classid()
/kernel/linux/linux-5.10/arch/arm64/mm/
Dmmap.c32 * entire range. In theory, this could lead to false negatives in valid_phys_addr_range()
/kernel/linux/linux-5.10/arch/arm/
DKconfig914 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
952 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
958 optimisation in the Cortex-A9 Store Buffer may lead to data
1025 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
1061 lead to either a data corruption or a CPU deadlock. Not fixed in
1068 bool "ARM errata: A12: sequence of VMOV to core registers might lead to a dead lock"
1074 one is in the shadow of a branch or abort, can lead to a
1109 lead to either a data corruption or a CPU deadlock. Not fixed in
/kernel/linux/linux-5.10/Documentation/driver-api/md/
Draid5-ppl.rst9 disks is missing. This can lead to silent data corruption when rebuilding the
/kernel/linux/linux-5.10/security/tomoyo/
DKconfig49 operations which can lead to the hijacking of the boot sequence are
/kernel/linux/linux-5.10/arch/s390/include/asm/
Dftrace.h94 * different system call table is used for compat tasks. This may lead
/kernel/linux/linux-5.10/drivers/net/ethernet/ibm/ehea/
Dehea_qmr.h145 /* Defines which bad send cqe stati lead to a port reset */
185 /* Defines which affiliated errors lead to a port reset */
/kernel/linux/linux-5.10/Documentation/core-api/
Dgfp_mask-from-fs-io.rst25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory

12345678910>>...23