New issue
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
Reduce the number of search_exception_tables in valid kernel fault path #317
Comments
See series at https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=194507&state=* Is that what you had in mind ? |
Oh nice, yeah that looks pretty good. I will try to review it in time for the next merge window. |
This is mainly rebasing on top of Aneesh's changes I droped the last patch (removal of bad_kuap_fault() warnings) as it doesn't make consensus. We'll see in a second step, maybe we could keep those warnings only when CONFIG_PPC_KUAP_DEBUG is set. |
Can this be closed? |
Yeah I think so, merged as of: torvalds/linux@5f1888a I didn't take the removal of the bad_kuap_fault() warnings, that can be a new issue if it needs to be. |
They have been removed, see torvalds/linux@3dc12df |
OK, what do I know 😛 We still have a WARN in |
Yes that has allowed us to get the search_exception_table() out of the fast path, so everyone is happy :) |
copy_to/from_user taking valid page faults should have good performance.
This currently searches exception tables at least once for no pte faults, at least twice for prot faults, and sometimes 3 times. This is easy to consolidate the prot fault case to one.
The search is used as a poor man's KUAP and provides almost no benefit if real KUAP is enabled, it could be avoided completely in that case.
The search after mmap_read_trylock is still necessary as the comment explains.
The text was updated successfully, but these errors were encountered: