| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| 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-6.12.1/net/wireless/ |
| D | wext-spy.c | 34 /* Make sure driver is not buggy or using the old API */ in iw_handler_set_spy()
83 /* Make sure driver is not buggy or using the old API */ in iw_handler_get_spy()
118 /* Make sure driver is not buggy or using the old API */ in iw_handler_set_thrspy()
145 /* Make sure driver is not buggy or using the old API */ in iw_handler_get_thrspy()
200 /* Make sure driver is not buggy or using the old API */ in wireless_spy_update()
|
| /linux-6.12.1/mm/kasan/ |
| D | report_tags.c | 48 * buggy object. This is a best-effort process. in kasan_complete_mode_report_info()
51 * the buggy object. Also, since the number of entries is limited, the in kasan_complete_mode_report_info()
52 * entries relevant to the buggy object can be overwritten. in kasan_complete_mode_report_info()
|
| D | report.c | 299 pr_err("The buggy address belongs to the object at %px\n" in describe_object_addr()
328 pr_err("The buggy address is located %d bytes %s of\n" in describe_object_addr()
386 pr_err("The buggy address belongs to the variable:\n"); in print_address_description()
404 pr_err("The buggy address belongs to the virtual mapping at\n" in print_address_description()
415 pr_err("The buggy address belongs to the physical page:\n"); in print_address_description()
429 * Memory state around the buggy address: in meta_pointer_offset()
450 pr_err("Memory state around the buggy address:\n"); in print_memory_metadata()
|
| /linux-6.12.1/Documentation/translations/zh_TW/dev-tools/ |
| D | kasan.rst | 190 The buggy address belongs to the object at ffff8801f44ec300
192 The buggy address is located 123 bytes inside of
194 The buggy address belongs to the page:
201 Memory state around the buggy address:
|
| /linux-6.12.1/samples/livepatch/ |
| D | livepatch-shadow-mod.c | 7 * livepatch-shadow-mod.c - Shadow variables, buggy module demo
25 * Step 1 - Load the buggy demonstration module:
74 MODULE_DESCRIPTION("Buggy module for shadow variable demo");
|
| /linux-6.12.1/Documentation/translations/zh_CN/dev-tools/ |
| D | kasan.rst | 190 The buggy address belongs to the object at ffff8801f44ec300
192 The buggy address is located 123 bytes inside of
194 The buggy address belongs to the page:
201 Memory state around the buggy address:
|
| /linux-6.12.1/drivers/tty/serial/8250/ |
| D | 8250.h | 90 #define UART_BUG_QUOT BIT(0) /* UART has buggy quot LSB */
91 #define UART_BUG_TXEN BIT(1) /* UART has buggy TX IIR status */
92 #define UART_BUG_NOMSR BIT(2) /* UART has buggy MSR status bits (Au1x00) */
93 #define UART_BUG_THRE BIT(3) /* UART has buggy THRE reassertion */
|
| /linux-6.12.1/arch/x86/platform/efi/ |
| D | quirks.c | 239 * buggy implementations we reserve boot services region during EFI
383 * (duplicate) 1:1 mappings were also created as a quirk for buggy firmware. So,
437 * code/data regions were mapped as a quirk for buggy firmware. in efi_free_boot_services()
741 * Service is buggy. in efi_crash_gracefully_on_page_fault()
747 * Buggy efi_reset_system() is handled differently from other EFI in efi_crash_gracefully_on_page_fault()
755 pr_info("efi_reset_system() buggy! Reboot through BIOS\n"); in efi_crash_gracefully_on_page_fault()
|
| /linux-6.12.1/tools/testing/selftests/net/netfilter/packetdrill/ |
| D | conntrack_synack_old.pkt | 3 // tcpdump with buggy sequence
37 // with buggy conntrack above packet is dropped, so SYN rtx is seen:
|
| /linux-6.12.1/sound/soc/intel/common/ |
| D | soc-acpi-intel-cht-match.c | 54 * Some tablets with Android factory OS have buggy DSDTs with an ESSX8316 device
79 * The Lenovo Yoga Tab 3 Pro YT3-X90, with Android factory OS has a buggy DSDT
|
| /linux-6.12.1/arch/powerpc/sysdev/ |
| D | dart_iommu.c | 96 "time. Buggy U3 ?"); in dart_tlb_invalidate_all()
128 "time. Buggy U4 ?"); in dart_tlb_invalidate_one()
214 * not doing it is that we won't catch buggy device drivers doing in dart_free()
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| 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-6.12.1/drivers/clocksource/ |
| D | i8253.c | 75 * buggy, so we just do the simple thing now. in i8253_read()
127 * the IRQ is stopped on those buggy virt implementations. And then in clockevent_i8253_disable()
|
| /linux-6.12.1/tools/perf/tests/ |
| D | perf-hooks.c | 43 /* the buggy hook is removed? */ in test__perf_hooks()
|
| /linux-6.12.1/arch/sparc/include/asm/ |
| D | pci.h | 7 * already-configured bus numbers - to be used for buggy BIOSes
|
| /linux-6.12.1/drivers/mmc/core/ |
| D | quirks.h | 143 * is used so disable the HPI feature for such buggy cards.
149 * feature is used so disable the HPI feature for such buggy cards.
|
| /linux-6.12.1/arch/xtensa/include/asm/ |
| D | pci.h | 15 * already-configured bus numbers - to be used for buggy BIOSes
|
| /linux-6.12.1/include/acpi/platform/ |
| D | acgccex.h | 14 * Some versions of gcc implement strchr() with a buggy macro. So,
|
| /linux-6.12.1/arch/x86/kernel/fpu/ |
| D | bugs.c | 21 * be buggy. So let's have a correct XMM trap
|
| /linux-6.12.1/tools/testing/selftests/net/packetdrill/ |
| 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-6.12.1/include/asm-generic/ |
| D | bitops.h | 9 * out before rolling your own buggy implementation in assembly language.
|
| /linux-6.12.1/drivers/pnp/pnpbios/ |
| D | Kconfig | 35 Also some buggy systems will fault when accessing certain features
|
| /linux-6.12.1/include/linux/ |
| D | smc91x.h | 43 bool pxa_u16_align4; /* PXA buggy u16 writes on 4*n+2 addresses */
|
| /linux-6.12.1/drivers/parisc/ |
| D | led.c | 451 * KittyHawk machines have often a buggy PDC, so that we explicitly check
464 /* Work around the buggy PDC of KittyHawk-machines */ in early_led_init()
488 /* check the results. Some machines have a buggy PDC */ in early_led_init()
|