We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the frame allocator to map pages with USER_ACCESSIBLE will create new p3 and p2 pages without USER_ACCESSIBLE.
I had to change
x86_64/src/structures/paging/mapper/mapped_page_table.rs
Lines 463 to 466 in fef3b4f
to
entry.set_frame( frame.frame(), PageTableFlags::PRESENT | PageTableFlags::WRITABLE | PageTableFlags::USER_ACCESSIBLE, );
Otherwise a ring3 cannot access the page.
Not sure, if the code traversing the p2 and p3 should also check for USER_ACCESSIBLE and correct that.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! We're already working on a solution to this in #112. Maybe you can help us find a good solution?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Using the frame allocator to map pages with USER_ACCESSIBLE will create new p3 and p2 pages without USER_ACCESSIBLE.
I had to change
x86_64/src/structures/paging/mapper/mapped_page_table.rs
Lines 463 to 466 in fef3b4f
to
Otherwise a ring3 cannot access the page.
Not sure, if the code traversing the p2 and p3 should also check for USER_ACCESSIBLE and correct that.
The text was updated successfully, but these errors were encountered: