-
Notifications
You must be signed in to change notification settings - Fork 126
ftrace: fix incorrect hash size in register_ftrace_direct() #8788
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
Conversation
Upstream branch: a650d38 |
Upstream branch: a650d38 |
4dbc0da
to
4785a01
Compare
2bd694b
to
9cf4748
Compare
Upstream branch: 8ffd015 |
4785a01
to
936bd1b
Compare
Upstream branch: 8ffd015 |
936bd1b
to
a899fef
Compare
9cf4748
to
a4f0750
Compare
The maximum of the ftrace hash bits is made fls(32) in register_ftrace_direct(), which seems illogical. So, we fix it by making the max hash bits FTRACE_HASH_MAX_BITS instead. Fixes: d05cb47 ("ftrace: Fix modification of direct_function hash while in use") Signed-off-by: Menglong Dong <[email protected]> Acked-by: Masami Hiramatsu (Google) <[email protected]>
Upstream branch: 834a4a6 |
a899fef
to
911980b
Compare
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=952788 irrelevant now. Closing PR. |
Pull request for series with
subject: ftrace: fix incorrect hash size in register_ftrace_direct()
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=952720