| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 22 exceptional buggy platforms, special restrictions and exceptions should be
31 However the word of "current" has ambiguity, some buggy AML tables return
42 There are buggy AML tables never notifying when the lid device state is
66 triggered events to the userspace. However, given the fact that the buggy
85 isn't ready to handle the buggy AML tables.
114 handle the buggy AML tables.
|
| /linux/tools/testing/selftests/net/netfilter/packetdrill/ |
| H A D | conntrack_synack_old.pkt | 3 // tcpdump with buggy sequence
37 // with buggy conntrack above packet is dropped, so SYN rtx is seen:
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_md5_md5-only-on-client-ack.pkt | 19 // The TCP listener refcount should be 2, but on buggy kernels it can be 0:
|
| /linux/drivers/pnp/pnpbios/ |
| H A D | Kconfig | 35 Also some buggy systems will fault when accessing certain features
|
| /linux/Documentation/hwmon/ |
| H A D | asus_wmi_sensors.rst | 69 * The WMI implementation in some of Asus' BIOSes is buggy. This can result in
|
| /linux/tools/kvm/kvm_stat/ |
| H A D | kvm_stat.txt | 19 Often conclusions about performance or buggy behavior can be drawn from the
|
| /linux/fs/jffs2/ |
| H A D | debug.c | 707 int buggy = 0; in __jffs2_dbg_dump_fragtree_nolock() local
721 buggy = 1; in __jffs2_dbg_dump_fragtree_nolock()
729 if (buggy) { in __jffs2_dbg_dump_fragtree_nolock()
|
| /linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 312 buggy lockless writes, read_foo_diagnostic() can be updated as follows:
327 However, in order for KCSAN to detect buggy lockless writes, your kernel
367 of the ASSERT_EXCLUSIVE_WRITER() is to allow KCSAN to check for a buggy
534 ASSERT_EXCLUSIVE_ACCESS() allows KCSAN to flag buggy concurrent unmarked
536 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| /linux/Documentation/power/ |
| H A D | s2ram.rst | 21 always it's a driver that is buggy. Thank God for the suspend/resume
|
| /linux/Documentation/admin-guide/acpi/ |
| H A D | initrd_table_override.rst | 37 allows you to upgrade the buggy tables before your platform/BIOS vendor
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-ata | 139 be buggy and only unqueued TRIM commands
|
| /linux/Documentation/locking/ |
| H A D | locktorture.rst | 50 Simulates a buggy lock implementation.
|
| /linux/Documentation/power/regulator/ |
| H A D | overview.rst | 166 overvoltage or overcurrent caused by buggy client drivers. It also
|
| /linux/Documentation/networking/device_drivers/fddi/ |
| H A D | skfp.rst | 213 - Synchronization on SMP machines was buggy
|
| /linux/Documentation/scheduler/ |
| H A D | sched-nice-design.rst | 86 proof, and a buggy SCHED_FIFO app can also lock up the system for good.
|
| /linux/Documentation/sound/designs/ |
| H A D | procfile.rst | 120 buggy) hardware that doesn't give smooth pointer updates.
|
| /linux/arch/powerpc/kvm/ |
| H A D | Kconfig | 171 those buggy L1s which saves the L2 state, at the cost of performance
|
| /linux/Documentation/filesystems/ |
| H A D | hpfs.rst | 120 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
136 would cause more problems than benefit with such buggy implementation in OS/2.
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-class-tpm | 64 Durations can be modified in the case where a buggy chip
|
| /linux/Documentation/input/devices/ |
| H A D | iforce-protocol.rst | 370 At first glance, this software seems, hum, well... buggy. In fact, data appear with a
|
| /linux/Documentation/RCU/ |
| H A D | rcu_dereference.rst | 89 the following (quite strange) code is buggy::
101 As before, the reason this is buggy is that relational operators
|
| /linux/Documentation/arch/m68k/ |
| H A D | buddha-driver.rst | 87 a buggy firmware and pull the IRQ line up
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 631 Guys, whether something was buggy or not DOES NOT MATTER.
648 Anybody who uses "but it was buggy" as an argument is entirely missing
649 the point. As far as the USER was concerned, it wasn't buggy - it
744 actually buggy. In fact, it was doing exactly what it set out to do,
|
| /linux/Documentation/arch/x86/ |
| H A D | tdx.rst | 124 machine's runtime. A non-buggy BIOS should never support hot-removal of
138 enabling TDX. A non-buggy BIOS should never support hot-add/removal of
|
| /linux/Documentation/networking/ |
| H A D | msg_zerocopy.rst | 31 is not affected, but a buggy program can possibly corrupt its own data
|