summaryrefslogtreecommitdiff
path: root/contrib/webcscope/icons/CVS/Entries.Old
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/webcscope/icons/CVS/Entries.Old')
-rw-r--r--contrib/webcscope/icons/CVS/Entries.Old0
1 files changed, 0 insertions, 0 deletions
diff --git a/contrib/webcscope/icons/CVS/Entries.Old b/contrib/webcscope/icons/CVS/Entries.Old
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/contrib/webcscope/icons/CVS/Entries.Old
he user disable and enable patch again, there is possible bug in klp_enable_func. If the user specified func->old_addr for some function in the module (and he shouldn't do that, but nevertheless) our warning would not catch it, ftrace will reject to register the handler because of wrong address or will register the handler for wrong address. 2) relocations are applied successfully, but kallsyms lookup fails. In this case func->old_addr can be correct for all previous lookups, 0 for current failed one, and "unspecified" for the rest. If we undergo the same scenario as in 1, the behaviour differs for three cases, but the patch is not enabled anyway. 3) the object is initialized, but klp_enable_object fails in the notifier due to possible ftrace error. Since it is improbable that ftrace would heal itself in the future, we would get those errors everytime the patch is enabled. In order to fix above situations, we can make obj->mod to NULL, if the coming modified notifier fails. Signed-off-by: Minfei Huang <mnfhuang@gmail.com> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com> Reviewed-by: Miroslav Benes <mbenes@suse.cz> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'kernel/livepatch')