mirror of
https://github.com/RGBCube/serenity
synced 2025-07-23 14:07:42 +00:00
Kernel/Memory: Fix UNMAP_AFTER_INIT page fault handling
This was discovered by me during a work on USB keyboard patches, so it triggered this bug. The printing format for the VirtualAddress part is incorrect, leading to another crash when handling page fault after accessing UNMAP_AFTER_INIT code section.
This commit is contained in:
parent
c4ef1db33d
commit
36bb04d792
1 changed files with 1 additions and 1 deletions
|
@ -740,7 +740,7 @@ PageFaultResponse MemoryManager::handle_page_fault(PageFault const& fault)
|
||||||
|
|
||||||
if (faulted_in_range(&start_of_unmap_after_init, &end_of_unmap_after_init)) {
|
if (faulted_in_range(&start_of_unmap_after_init, &end_of_unmap_after_init)) {
|
||||||
auto const* kernel_symbol = symbolicate_kernel_address(fault.vaddr().get());
|
auto const* kernel_symbol = symbolicate_kernel_address(fault.vaddr().get());
|
||||||
dbgln("Attempt to access UNMAP_AFTER_INIT section ({:p}: {})", fault.vaddr(), kernel_symbol ? kernel_symbol->name : "(Unknown)");
|
dbgln("Attempt to access UNMAP_AFTER_INIT section ({}: {})", fault.vaddr(), kernel_symbol ? kernel_symbol->name : "(Unknown)");
|
||||||
return PageFaultResponse::ShouldCrash;
|
return PageFaultResponse::ShouldCrash;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue