-
Notifications
You must be signed in to change notification settings - Fork 300
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
changes to .kprobes.text not detected #150
Comments
Hm, maybe the "no changed functions were found" check happens before the "some unexpected section changed" check? |
Yeah, with a bigger patch that changes another non-kprobes function, I get the error I expected:
|
jpoimboe
added a commit
to jpoimboe/kpatch
that referenced
this issue
Apr 29, 2014
If a patch changes a single function which is in a special section that we don't support, create-diff-object reports "no changed functions were found". Give a clearer error message in that case, by checking reachability errors before unchanged errors and by printing all reachability errors errors instead of the first one it encounters. Fixes dynup#150.
jpoimboe
added a commit
to jpoimboe/kpatch
that referenced
this issue
Apr 29, 2014
If a patch changes a single function which is in a special section that we don't support, create-diff-object reports "no changed functions were found". Give a clearer error message in that case, by checking reachability errors before unchanged errors and by printing all reachability errors errors instead of the first one it encounters. Fixes dynup#150.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the following patch, kpatch-build doesn't detect any changes:
I think it's because do_nmi() is annotated with __kprobes which places it in the .kprobes.text section. But I'd expect the inclusion logic to catch the fact that .kprobes.text changed and report an error.
The text was updated successfully, but these errors were encountered: