Searched refs:lead (Results 1 – 25 of 122) sorted by relevance
12345
| /Linux-v5.4/Documentation/process/ |
| D | deprecated.rst | 36 risk of them overflowing. This could lead to values wrapping around and a
38 allocations could lead to linear overflows of heap memory and other
74 explicitly ignore overflows, which may lead to unexpected results
92 will be NUL terminated. This can lead to various linear read overflows
108 the given limit of bytes to copy. This is inefficient and can lead to
119 lead to a crash, possible overwriting sensitive contents at the end of the
|
| D | 7.AdvancedTopics.rst | 79 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
|
| /Linux-v5.4/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()
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v5.4/Documentation/ide/ |
| D | warm-plug-howto.rst | 18 results may be unpredictable and lead to data loss if you're unlucky
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/i2c/ |
| D | adv7343.txt | 3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | adm1026.rst | 96 voltage from the power lead rather than on the ground lead.
|
| /Linux-v5.4/drivers/media/pci/ddbridge/ |
| D | Kconfig | 41 might lead to I2C errors originating from the bridge in conjunction
|
| /Linux-v5.4/drivers/eisa/ |
| D | Kconfig | 48 # an X86 may lead to crashes...
|
| /Linux-v5.4/scripts/ |
| D | checkpatch.pl | 4838 my $lead = $1;
4843 if ($lead !~ /(?:$Operators|\.)\s*$/ &&
5692 my $lead = $fixed[$fixlinenr] =~
5694 $lead = rtrim($1);
5695 $lead = "$lead " if ($lead !~ /^\+$/);
5696 $lead = "${lead}const ";
5697 $fixed[$fixlinenr] =~ s/(^\+\s*(?:static\s+))/$lead/;
6419 my $lead = $1;
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cpu-load.rst | 52 will lead to quite erratic information inside ``/proc/stat``::
|
| D | security-bugs.rst | 62 Fixes for sensitive bugs, such as those that might lead to privilege
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 137 The same lock-class must not be acquired twice, because this could lead
145 because this could lead to a deadlock - referred to as lock inversion
147 could lead to the two contexts waiting for each other permanently. The
186 could lead to a lock inversion deadlock - even if that lock scenario did
|
| /Linux-v5.4/security/tomoyo/ |
| D | Kconfig | 49 operations which can lead to the hijacking of the boot sequence are
|
| /Linux-v5.4/scripts/coccinelle/null/ |
| D | badzero.cocci | 120 // This rule may lead to inconsistent path problems, if E is defined in two
|
| /Linux-v5.4/Documentation/misc-devices/ |
| D | apds990x.txt | 29 lead to false interrupt, but that doesn't harm.
|
| /Linux-v5.4/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
|
| D | idr.rst | 61 you may need to pass a restrictive set of GFP flags, which can lead
|
| /Linux-v5.4/Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 9 disks is missing. This can lead to silent data corruption when rebuilding the
|
| /Linux-v5.4/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 25 ADI registers will make ADI controller registers chaos to lead incorrect results.
|
| /Linux-v5.4/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 55 possible in a single segment setup, but this can lead to synchronization
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 31 rdma resources. This can lead to service unavailability.
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 106 so this would lead to the same effect as case i) now.
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | setox.S | 505 fmuls #0xBC317218,%fp0 | ...N * L1, L1 = lead(-log2/64)
545 fmovex (%a1)+,%fp1 | ...fp1 is lead. pt. of 2^(J/64)
671 fmuls #0xBC317218,%fp0 | ...N * L1, L1 = lead(-log2/64)
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-domains.rst | 14 although strictly it doesn't have to, but this could lead to a case where some
|
12345
