| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/drivers/ide/ |
| D | rz1000.c | 11 * This file provides support for disabling the buggy read-ahead
33 "(buggy RZ1000/RZ1001)\n", pci_name(dev)); in rz1000_disable_readahead()
37 "(buggy RZ1000/RZ1001)\n", pci_name(dev)); in rz1000_disable_readahead()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/mm/kasan/ |
| D | report_tags.c | 51 * buggy object. This is a best-effort process. in kasan_complete_mode_report_info()
54 * the buggy object. Also, since the number of entries is limited, the in kasan_complete_mode_report_info()
55 * entries relevant to the buggy object can be overwritten. in kasan_complete_mode_report_info()
|
| D | report.c | 286 pr_err("The buggy address belongs to the object at %px\n" in describe_object_addr()
315 pr_err("The buggy address is located %d bytes %s of\n" in describe_object_addr()
373 pr_err("The buggy address belongs to the variable:\n"); in print_address_description()
388 pr_err("The buggy address belongs to a"); in print_address_description()
395 pr_err("The buggy address belongs to the physical page:\n"); in print_address_description()
409 * Memory state around the buggy address: in meta_pointer_offset()
430 pr_err("Memory state around the buggy address:\n"); in print_memory_metadata()
|
| /kernel/linux/linux-6.6/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:
|
| /kernel/linux/linux-6.6/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");
|
| /kernel/linux/linux-5.10/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");
|
| /kernel/linux/linux-5.10/drivers/tty/serial/8250/ |
| D | 8250.h | 86 #define UART_BUG_QUOT (1 << 0) /* UART has buggy quot LSB */
87 #define UART_BUG_TXEN (1 << 1) /* UART has buggy TX IIR status */
88 #define UART_BUG_NOMSR (1 << 2) /* UART has buggy MSR status bits (Au1x00) */
89 #define UART_BUG_THRE (1 << 3) /* UART has buggy THRE reassertion */
|
| /kernel/linux/linux-6.6/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 */
|
| /kernel/linux/linux-5.10/arch/x86/platform/efi/ |
| D | quirks.c | 231 * buggy implementations we reserve boot services region during EFI
375 * (duplicate) 1:1 mappings were also created as a quirk for buggy firmware. So,
429 * code/data regions were mapped as a quirk for buggy firmware. in efi_free_boot_services()
711 * Service is buggy. in efi_recover_from_page_fault()
717 * Buggy efi_reset_system() is handled differently from other EFI in efi_recover_from_page_fault()
725 pr_info("efi_reset_system() buggy! Reboot through BIOS\n"); in efi_recover_from_page_fault()
|
| /kernel/linux/linux-5.10/mm/kasan/ |
| D | report.c | 138 pr_err("The buggy address belongs to the object at %px\n" in describe_object_addr()
156 pr_err("The buggy address is located %d bytes %s of\n" in describe_object_addr()
388 pr_err("The buggy address belongs to the variable:\n"); in print_address_description()
393 pr_err("The buggy address belongs to the page:\n"); in print_address_description()
424 pr_err("Memory state around the buggy address:\n"); in print_shadow_for_address()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kasan.rst | 111 The buggy address belongs to the object at ffff8801f44ec300
113 The buggy address is located 123 bytes inside of
115 The buggy address belongs to the page:
122 Memory state around the buggy address:
|
| /kernel/linux/linux-5.10/arch/ia64/scripts/ |
| D | check-gas | 12 echo buggy
|
| /kernel/linux/linux-6.6/arch/ia64/scripts/ |
| D | check-gas | 12 echo buggy
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 289 buggy lockless writes, read_foo_diagnostic() can be updated as follows:
304 However, in order for KCSAN to detect buggy lockless writes, your kernel
344 of the ASSERT_EXCLUSIVE_WRITER() is to allow KCSAN to check for a buggy
511 ASSERT_EXCLUSIVE_ACCESS() allows KCSAN to flag buggy concurrent unmarked
513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| /kernel/linux/linux-5.10/drivers/mmc/core/ |
| D | quirks.h | 128 * is used so disable the HPI feature for such buggy cards.
134 * feature is used so disable the HPI feature for such buggy cards.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/arch/powerpc/sysdev/ |
| D | dart_iommu.c | 97 "time. Buggy U3 ?"); in dart_tlb_invalidate_all()
129 "time. Buggy U4 ?"); in dart_tlb_invalidate_one()
215 * not doing it is that we won't catch buggy device drivers doing in dart_free()
|
| /kernel/linux/linux-6.6/arch/powerpc/sysdev/ |
| D | dart_iommu.c | 97 "time. Buggy U3 ?"); in dart_tlb_invalidate_all()
129 "time. Buggy U4 ?"); in dart_tlb_invalidate_one()
215 * not doing it is that we won't catch buggy device drivers doing in dart_free()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/tools/perf/tests/ |
| D | perf-hooks.c | 43 /* the buggy hook is removed? */ in test__perf_hooks()
|