UPSTREAM: riscv: acpi: avoid errors caused by probing DT devices when… #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… ACPI is used
Similar to the ARM64 commit 3505f30fb6a9s ("ARM64 / ACPI: If we chose
to boot from acpi then disable FDT"), let's not do DT hardware probing
if ACPI is enabled in early boot. This avoids errors caused by
repeated driver probing.
Signed-off-by: Han Gao <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[[email protected]: cleaned up patch description and subject]
Signed-off-by: Paul Walmsley <[email protected]>
(cherry picked from commit 69a8b62)
Signed-off-by: Han Gao <[email protected]>
MingcongBai
pushed a commit
that referenced
this pull request
Oct 23, 2025
[ Upstream commit 48918ca ] The test starts a workload and then opens events. If the events fail to open, for example because of perf_event_paranoid, the gopipe of the workload is leaked and the file descriptor leak check fails when the test exits. To avoid this cancel the workload when opening the events fails. Before: ``` $ perf test -vv 7 7: PERF_RECORD_* events & perf_sample fields: --- start --- test child forked, pid 1189568 Using CPUID GenuineIntel-6-B7-1 ------------------------------------------------------------ perf_event_attr: type 0 (PERF_TYPE_HARDWARE) config 0xa00000000 (cpu_atom/PERF_COUNT_HW_CPU_CYCLES/) disabled 1 ------------------------------------------------------------ sys_perf_event_open: pid 0 cpu -1 group_fd -1 flags 0x8 sys_perf_event_open failed, error -13 ------------------------------------------------------------ perf_event_attr: type 0 (PERF_TYPE_HARDWARE) config 0xa00000000 (cpu_atom/PERF_COUNT_HW_CPU_CYCLES/) disabled 1 exclude_kernel 1 ------------------------------------------------------------ sys_perf_event_open: pid 0 cpu -1 group_fd -1 flags 0x8 = 3 ------------------------------------------------------------ perf_event_attr: type 0 (PERF_TYPE_HARDWARE) config 0x400000000 (cpu_core/PERF_COUNT_HW_CPU_CYCLES/) disabled 1 ------------------------------------------------------------ sys_perf_event_open: pid 0 cpu -1 group_fd -1 flags 0x8 sys_perf_event_open failed, error -13 ------------------------------------------------------------ perf_event_attr: type 0 (PERF_TYPE_HARDWARE) config 0x400000000 (cpu_core/PERF_COUNT_HW_CPU_CYCLES/) disabled 1 exclude_kernel 1 ------------------------------------------------------------ sys_perf_event_open: pid 0 cpu -1 group_fd -1 flags 0x8 = 3 Attempt to add: software/cpu-clock/ ..after resolving event: software/config=0/ cpu-clock -> software/cpu-clock/ ------------------------------------------------------------ perf_event_attr: type 1 (PERF_TYPE_SOFTWARE) size 136 config 0x9 (PERF_COUNT_SW_DUMMY) sample_type IP|TID|TIME|CPU read_format ID|LOST disabled 1 inherit 1 mmap 1 comm 1 enable_on_exec 1 task 1 sample_id_all 1 mmap2 1 comm_exec 1 ksymbol 1 bpf_event 1 { wakeup_events, wakeup_watermark } 1 ------------------------------------------------------------ sys_perf_event_open: pid 1189569 cpu 0 group_fd -1 flags 0x8 sys_perf_event_open failed, error -13 perf_evlist__open: Permission denied ---- end(-2) ---- Leak of file descriptor 6 that opened: 'pipe:[14200347]' ---- unexpected signal (6) ---- iFailed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon Failed to read build ID for //anon #0 0x565358f6666e in child_test_sig_handler builtin-test.c:311 #1 0x7f29ce849df0 in __restore_rt libc_sigaction.c:0 #2 0x7f29ce89e95c in __pthread_kill_implementation pthread_kill.c:44 #3 0x7f29ce849cc2 in raise raise.c:27 #4 0x7f29ce8324ac in abort abort.c:81 #5 0x565358f662d4 in check_leaks builtin-test.c:226 #6 0x565358f6682e in run_test_child builtin-test.c:344 #7 0x565358ef7121 in start_command run-command.c:128 #8 0x565358f67273 in start_test builtin-test.c:545 #9 0x565358f6771d in __cmd_test builtin-test.c:647 #10 0x565358f682bd in cmd_test builtin-test.c:849 #11 0x565358ee5ded in run_builtin perf.c:349 #12 0x565358ee6085 in handle_internal_command perf.c:401 #13 0x565358ee61de in run_argv perf.c:448 #14 0x565358ee6527 in main perf.c:555 torvalds#15 0x7f29ce833ca8 in __libc_start_call_main libc_start_call_main.h:74 torvalds#16 0x7f29ce833d65 in __libc_start_main@@GLIBC_2.34 libc-start.c:128 torvalds#17 0x565358e391c1 in _start perf[851c1] 7: PERF_RECORD_* events & perf_sample fields : FAILED! ``` After: ``` $ perf test 7 7: PERF_RECORD_* events & perf_sample fields : Skip (permissions) ``` Fixes: 16d00fe ("perf tests: Move test__PERF_RECORD into separate object") Signed-off-by: Ian Rogers <[email protected]> Tested-by: Arnaldo Carvalho de Melo <[email protected]> Cc: Adrian Hunter <[email protected]> Cc: Alexander Shishkin <[email protected]> Cc: Athira Rajeev <[email protected]> Cc: Chun-Tse Shao <[email protected]> Cc: Howard Chu <[email protected]> Cc: Ingo Molnar <[email protected]> Cc: James Clark <[email protected]> Cc: Jiri Olsa <[email protected]> Cc: Kan Liang <[email protected]> Cc: Mark Rutland <[email protected]> Cc: Namhyung Kim <[email protected]> Cc: Peter Zijlstra <[email protected]> Signed-off-by: Arnaldo Carvalho de Melo <[email protected]> Signed-off-by: Sasha Levin <[email protected]>
|
Now in |
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 23, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5-rc2 (HEAD: fbe142c47f94449ccc552bdee576361edc57cf81). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
7 tasks
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 23, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5-rc2 (HEAD: fbe142c47f94449ccc552bdee576361edc57cf81). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 23, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5-rc2 (HEAD: fbe142c47f94449ccc552bdee576361edc57cf81). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 25, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 27, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 27, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
pushed a commit
that referenced
this pull request
Oct 28, 2025
[ Upstream commit 738d5a5 ] hfsplus_bmap_alloc can trigger a crash if a record offset or length is larger than node_size [ 15.264282] BUG: KASAN: slab-out-of-bounds in hfsplus_bmap_alloc+0x887/0x8b0 [ 15.265192] Read of size 8 at addr ffff8881085ca188 by task test/183 [ 15.265949] [ 15.266163] CPU: 0 UID: 0 PID: 183 Comm: test Not tainted 6.17.0-rc2-gc17b750b3ad9 #14 PREEMPT(voluntary) [ 15.266165] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 15.266167] Call Trace: [ 15.266168] <TASK> [ 15.266169] dump_stack_lvl+0x53/0x70 [ 15.266173] print_report+0xd0/0x660 [ 15.266181] kasan_report+0xce/0x100 [ 15.266185] hfsplus_bmap_alloc+0x887/0x8b0 [ 15.266208] hfs_btree_inc_height.isra.0+0xd5/0x7c0 [ 15.266217] hfsplus_brec_insert+0x870/0xb00 [ 15.266222] __hfsplus_ext_write_extent+0x428/0x570 [ 15.266225] __hfsplus_ext_cache_extent+0x5e/0x910 [ 15.266227] hfsplus_ext_read_extent+0x1b2/0x200 [ 15.266233] hfsplus_file_extend+0x5a7/0x1000 [ 15.266237] hfsplus_get_block+0x12b/0x8c0 [ 15.266238] __block_write_begin_int+0x36b/0x12c0 [ 15.266251] block_write_begin+0x77/0x110 [ 15.266252] cont_write_begin+0x428/0x720 [ 15.266259] hfsplus_write_begin+0x51/0x100 [ 15.266262] cont_write_begin+0x272/0x720 [ 15.266270] hfsplus_write_begin+0x51/0x100 [ 15.266274] generic_perform_write+0x321/0x750 [ 15.266285] generic_file_write_iter+0xc3/0x310 [ 15.266289] __kernel_write_iter+0x2fd/0x800 [ 15.266296] dump_user_range+0x2ea/0x910 [ 15.266301] elf_core_dump+0x2a94/0x2ed0 [ 15.266320] vfs_coredump+0x1d85/0x45e0 [ 15.266349] get_signal+0x12e3/0x1990 [ 15.266357] arch_do_signal_or_restart+0x89/0x580 [ 15.266362] irqentry_exit_to_user_mode+0xab/0x110 [ 15.266364] asm_exc_page_fault+0x26/0x30 [ 15.266366] RIP: 0033:0x41bd35 [ 15.266367] Code: bc d1 f3 0f 7f 27 f3 0f 7f 6f 10 f3 0f 7f 77 20 f3 0f 7f 7f 30 49 83 c0 0f 49 29 d0 48 8d 7c 17 31 e9 9f 0b 00 00 66 0f ef c0 <f3> 0f 6f 0e f3 0f 6f 56 10 66 0f 74 c1 66 0f d7 d0 49 83 f8f [ 15.266369] RSP: 002b:00007ffc9e62d078 EFLAGS: 00010283 [ 15.266371] RAX: 00007ffc9e62d100 RBX: 0000000000000000 RCX: 0000000000000000 [ 15.266372] RDX: 00000000000000e0 RSI: 0000000000000000 RDI: 00007ffc9e62d100 [ 15.266373] RBP: 0000400000000040 R08: 00000000000000e0 R09: 0000000000000000 [ 15.266374] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 [ 15.266375] R13: 0000000000000000 R14: 0000000000000000 R15: 0000400000000000 [ 15.266376] </TASK> When calling hfsplus_bmap_alloc to allocate a free node, this function first retrieves the bitmap from header node and map node using node->page together with the offset and length from hfs_brec_lenoff ``` len = hfs_brec_lenoff(node, 2, &off16); off = off16; off += node->page_offset; pagep = node->page + (off >> PAGE_SHIFT); data = kmap_local_page(*pagep); ``` However, if the retrieved offset or length is invalid(i.e. exceeds node_size), the code may end up accessing pages outside the allocated range for this node. This patch adds proper validation of both offset and length before use, preventing out-of-bounds page access. Move is_bnode_offset_valid and check_and_correct_requested_length to hfsplus_fs.h, as they may be required by other functions. Reported-by: [email protected] Closes: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Yang Chenzhi <[email protected]> Reviewed-by: Viacheslav Dubeyko <[email protected]> Signed-off-by: Viacheslav Dubeyko <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Viacheslav Dubeyko <[email protected]> Signed-off-by: Sasha Levin <[email protected]>
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Oct 28, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
7 tasks
MingcongBai
pushed a commit
that referenced
this pull request
Nov 8, 2025
[ Upstream commit 738d5a5 ] hfsplus_bmap_alloc can trigger a crash if a record offset or length is larger than node_size [ 15.264282] BUG: KASAN: slab-out-of-bounds in hfsplus_bmap_alloc+0x887/0x8b0 [ 15.265192] Read of size 8 at addr ffff8881085ca188 by task test/183 [ 15.265949] [ 15.266163] CPU: 0 UID: 0 PID: 183 Comm: test Not tainted 6.17.0-rc2-gc17b750b3ad9 #14 PREEMPT(voluntary) [ 15.266165] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 15.266167] Call Trace: [ 15.266168] <TASK> [ 15.266169] dump_stack_lvl+0x53/0x70 [ 15.266173] print_report+0xd0/0x660 [ 15.266181] kasan_report+0xce/0x100 [ 15.266185] hfsplus_bmap_alloc+0x887/0x8b0 [ 15.266208] hfs_btree_inc_height.isra.0+0xd5/0x7c0 [ 15.266217] hfsplus_brec_insert+0x870/0xb00 [ 15.266222] __hfsplus_ext_write_extent+0x428/0x570 [ 15.266225] __hfsplus_ext_cache_extent+0x5e/0x910 [ 15.266227] hfsplus_ext_read_extent+0x1b2/0x200 [ 15.266233] hfsplus_file_extend+0x5a7/0x1000 [ 15.266237] hfsplus_get_block+0x12b/0x8c0 [ 15.266238] __block_write_begin_int+0x36b/0x12c0 [ 15.266251] block_write_begin+0x77/0x110 [ 15.266252] cont_write_begin+0x428/0x720 [ 15.266259] hfsplus_write_begin+0x51/0x100 [ 15.266262] cont_write_begin+0x272/0x720 [ 15.266270] hfsplus_write_begin+0x51/0x100 [ 15.266274] generic_perform_write+0x321/0x750 [ 15.266285] generic_file_write_iter+0xc3/0x310 [ 15.266289] __kernel_write_iter+0x2fd/0x800 [ 15.266296] dump_user_range+0x2ea/0x910 [ 15.266301] elf_core_dump+0x2a94/0x2ed0 [ 15.266320] vfs_coredump+0x1d85/0x45e0 [ 15.266349] get_signal+0x12e3/0x1990 [ 15.266357] arch_do_signal_or_restart+0x89/0x580 [ 15.266362] irqentry_exit_to_user_mode+0xab/0x110 [ 15.266364] asm_exc_page_fault+0x26/0x30 [ 15.266366] RIP: 0033:0x41bd35 [ 15.266367] Code: bc d1 f3 0f 7f 27 f3 0f 7f 6f 10 f3 0f 7f 77 20 f3 0f 7f 7f 30 49 83 c0 0f 49 29 d0 48 8d 7c 17 31 e9 9f 0b 00 00 66 0f ef c0 <f3> 0f 6f 0e f3 0f 6f 56 10 66 0f 74 c1 66 0f d7 d0 49 83 f8f [ 15.266369] RSP: 002b:00007ffc9e62d078 EFLAGS: 00010283 [ 15.266371] RAX: 00007ffc9e62d100 RBX: 0000000000000000 RCX: 0000000000000000 [ 15.266372] RDX: 00000000000000e0 RSI: 0000000000000000 RDI: 00007ffc9e62d100 [ 15.266373] RBP: 0000400000000040 R08: 00000000000000e0 R09: 0000000000000000 [ 15.266374] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 [ 15.266375] R13: 0000000000000000 R14: 0000000000000000 R15: 0000400000000000 [ 15.266376] </TASK> When calling hfsplus_bmap_alloc to allocate a free node, this function first retrieves the bitmap from header node and map node using node->page together with the offset and length from hfs_brec_lenoff ``` len = hfs_brec_lenoff(node, 2, &off16); off = off16; off += node->page_offset; pagep = node->page + (off >> PAGE_SHIFT); data = kmap_local_page(*pagep); ``` However, if the retrieved offset or length is invalid(i.e. exceeds node_size), the code may end up accessing pages outside the allocated range for this node. This patch adds proper validation of both offset and length before use, preventing out-of-bounds page access. Move is_bnode_offset_valid and check_and_correct_requested_length to hfsplus_fs.h, as they may be required by other functions. Reported-by: [email protected] Closes: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Yang Chenzhi <[email protected]> Reviewed-by: Viacheslav Dubeyko <[email protected]> Signed-off-by: Viacheslav Dubeyko <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Viacheslav Dubeyko <[email protected]> Signed-off-by: Sasha Levin <[email protected]>
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Nov 8, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Nov 9, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
MingcongBai
added a commit
to AOSC-Dev/aosc-os-abbs
that referenced
this pull request
Nov 9, 2025
- Refresh Loongson UART patchset to v6. - Refresh Surface patchset to 6.17. - Refresh SG2042/2044 patchset.[^1] - Backport an upstream fix for ACPI access error on RISC-V ACPI+DT platforms.[^2] - Refresh kernel configurations. - Revert to using deepin-origin KVM fixes for 3B6000 and 3C6000 families. - (loongarch64) Backport a fix for rust-bindgen failure. - Track patches at AOSC-Tracking/linux @ aosc/v6.17.5- (HEAD: 84c080e43bd2970b617f9c5a7e44224791c9be21). [^1]: AOSC-Tracking/linux#13 [^2]: AOSC-Tracking/linux#14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… ACPI is used
Similar to the ARM64 commit 3505f30fb6a9s ("ARM64 / ACPI: If we chose to boot from acpi then disable FDT"), let's not do DT hardware probing if ACPI is enabled in early boot. This avoids errors caused by repeated driver probing.
Link: https://lore.kernel.org/r/[email protected]
[[email protected]: cleaned up patch description and subject]
(cherry picked from commit 69a8b62)