Home
last modified time | relevance | path

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

12345678910>>...29

/linux-6.12.1/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()
/linux-6.12.1/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
/linux-6.12.1/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
/linux-6.12.1/Documentation/hwmon/
Dadm1026.rst96 voltage from the power lead rather than on the ground lead.
/linux-6.12.1/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.
/linux-6.12.1/Documentation/ABI/obsolete/
Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/linux-6.12.1/drivers/media/pci/ivtv/
Divtvfb.c380 u16 lead = 0, tail = 0; in ivtvfb_write() local
415 lead = 4 - ((unsigned long)dst & 3); in ivtvfb_write()
416 if (copy_from_user(dst, buf, lead)) in ivtvfb_write()
418 buf += lead; in ivtvfb_write()
419 dst += lead; in ivtvfb_write()
422 if ((count - lead) & 3) in ivtvfb_write()
423 tail = (count - lead) & 3; in ivtvfb_write()
425 dma_size = count - lead - tail; in ivtvfb_write()
427 p + lead + dma_offset, (void __user *)buf, dma_size); in ivtvfb_write()
/linux-6.12.1/drivers/firmware/efi/
Dunaccepted_memory.c62 * load_unaligned_zeropad() can lead to unwanted loads across page in accept_memory()
69 * load from unaccepted memory will not lead to a recoverable exception in accept_memory()
/linux-6.12.1/tools/perf/util/
Dsharded_mutex.h12 * where the mutex is looked up from a hash value. This can lead to collisions
/linux-6.12.1/drivers/clk/qcom/
Dclk-regmap-phy-mux.h18 * which in turn would lead to disabling corresponding pipe_clk_src (and thus
/linux-6.12.1/arch/powerpc/mm/book3s64/
DMakefile23 # Instrumenting the SLB fault path can lead to duplicate SLB entries
/linux-6.12.1/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.dts22 * and the lowest PWM duty cycle that doesn't lead to backlight being off
/linux-6.12.1/arch/arm64/kernel/
Dwatchdog_hld.c11 * hand, we can't make it much higher as it would lead to a large hard-lockup
/linux-6.12.1/drivers/media/pci/ddbridge/
DKconfig40 might lead to I2C errors originating from the bridge in conjunction
/linux-6.12.1/Documentation/filesystems/xfs/
Dxfs-maintainer-entry-profile.rst63 - **Testing Lead**: This person is responsible for setting the test
68 The testing lead should identify themselves with an ``M:`` entry in
/linux-6.12.1/arch/x86/include/asm/
Dacenv.h22 * sleep state and cannot lead to data loss.
/linux-6.12.1/arch/arm/
DKconfig619 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
660 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
666 optimisation in the Cortex-A9 Store Buffer may lead to data
750 bool "ARM errata: A data cache maintenance operation which aborts, might lead to deadlock"
786 lead to either a data corruption or a CPU deadlock. Not fixed in
793 bool "ARM errata: A12: sequence of VMOV to core registers might lead to a dead lock"
799 one is in the shadow of a branch or abort, can lead to a
834 lead to either a data corruption or a CPU deadlock. Not fixed in
/linux-6.12.1/drivers/eisa/
DKconfig47 # Using EISA_VIRTUAL_ROOT on something other than an X86 may lead
/linux-6.12.1/net/dsa/
Dtag_hellcreek.c27 * avoid including it in calculations. That would lead to wrong in hellcreek_xmit()
/linux-6.12.1/Documentation/devicetree/bindings/media/i2c/
Dadv7343.txt3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
/linux-6.12.1/tools/testing/selftests/bpf/prog_tests/
Dxdp_dev_bound_only.c23 * This might lead to 'BUG: kernel NULL pointer dereference'.
/linux-6.12.1/include/net/
Dcls_cgroup.h59 * would lead to false results. in task_get_classid()
/linux-6.12.1/tools/testing/selftests/bpf/progs/
Dtimer_failure.c34 * skipping r0 = 0; should lead to a failure, but if exit in timer_cb_ret_bad()
/linux-6.12.1/drivers/gpu/drm/i915/
Di915_switcheroo.c47 * FIXME: open_count is protected by drm_global_mutex but that would lead to in i915_switcheroo_can_switch()

12345678910>>...29