Home
last modified time | relevance | path

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

12345678910>>...50

/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-6.6/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
/kernel/linux/linux-6.6/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
116 explicitly ignore overflows, which may lead to unexpected results
137 be NUL terminated. This can lead to various linear read overflows and
160 size limit. This is both inefficient and can lead to linear read overflows
167 Traditionally, using "%p" in format strings would lead to regular address
196 lead to a crash, possible overwriting sensitive contents at the end of the
/kernel/linux/linux-6.6/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/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-6.6/Documentation/hwmon/
Dadm1026.rst96 voltage from the power lead rather than on the ground lead.
/kernel/linux/linux-5.10/Documentation/hwmon/
Dadm1026.rst96 voltage from the power lead rather than on the ground lead.
/kernel/linux/linux-6.6/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/kernel/linux/linux-5.10/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/kernel/linux/linux-6.6/Documentation/kbuild/
Dreproducible-builds.rst125 Uncommitted changes or different commit ids in git can also lead
129 will be different, which will eventually lead to binary differences.
/kernel/linux/linux-6.6/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/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-6.6/drivers/firmware/efi/
Dunaccepted_memory.c60 * load_unaligned_zeropad() can lead to unwanted loads across page in accept_memory()
67 * load from unaccepted memory will not lead to a recoverable exception in accept_memory()
/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-6.6/tools/perf/util/
Dsharded_mutex.h12 * where the mutex is looked up from a hash value. This can lead to collisions
/kernel/linux/linux-6.6/drivers/clk/qcom/
Dclk-regmap-phy-mux.h18 * which in turn would lead to disabling corresponding pipe_clk_src (and thus
/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-6.6/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
/kernel/linux/linux-6.6/arch/arm64/kernel/
Dwatchdog_hld.c11 * hand, we can't make it much higher as it would lead to a large hard-lockup
/kernel/linux/linux-6.6/arch/powerpc/mm/book3s64/
DMakefile25 # Instrumenting the SLB fault path can lead to duplicate SLB entries
/kernel/linux/linux-5.10/drivers/media/pci/ddbridge/
DKconfig40 might lead to I2C errors originating from the bridge in conjunction

12345678910>>...50