You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current approach of trying to include the tracepoint-related
sections doesn't work at all. The new tracepoints don't show up in
"perf list".
And also, with one patch (issue dynup#219) I've seen a panic in
jump_label_del_module(). I suspect it's because the kernel is confused
by dynamic relocations' changing of the jump table after it was
registered with the jump table code.
I think the best approach for now is to just always exclude these
sections. It should be harmless, with the only consequence being that
tracepoints and jump labels can't be enabled in patched functions (which
is already the case with the current code anyway).
Fixesdynup#221.
The patching of jump label affected functions isn't actually supported
by the upstream kernel. So kpatch-build will warn if a function uses
jump labels.
I hex edited the original version of this test to remove the jump table
references to make it pass.
I believe the original objects were created with the following patch,
originally for dynup/kpatch#221.
Index: kernel-rhel7/net/core/dev.c
===================================================================
--- kernel-rhel7.orig/net/core/dev.c
+++ kernel-rhel7/net/core/dev.c
@@ -4199,6 +4199,7 @@ skip_classify:
case RX_HANDLER_PASS:
break;
default:
+ printk("BUG!\n");
BUG();
}
}
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
With the patch from #219 and the fix from #220, I get the following error:
The text was updated successfully, but these errors were encountered: