kpatch/test/integration/fedora-25/data-read-mostly.patch

diff -Nupr src.orig/net/core/dev.c src/net/core/dev.c
--- src.orig/net/core/dev.c	2016-11-30 19:39:45.232737234 +0000
+++ src/net/core/dev.c	2016-11-30 19:40:02.077737234 +0000
@@ -4179,6 +4179,7 @@ ncls:
 		case RX_HANDLER_PASS:
 			break;
 		default:
+			printk("BUG!\n");
 			BUG();
 		}
 	}
testing: rebase integration tests for Fedora 25 Kernel version 4.8.6-300.fc25.x86_64 2016-12-05 14:43:22 +00:00			`diff -Nupr src.orig/net/core/dev.c src/net/core/dev.c`
			`--- src.orig/net/core/dev.c 2016-11-30 19:39:45.232737234 +0000`
			`+++ src/net/core/dev.c 2016-11-30 19:40:02.077737234 +0000`
			`@@ -4179,6 +4179,7 @@ ncls:`
create-diff-object: tracepoint & jump label fixes 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 #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). Fixes #221. 2014-05-30 13:35:44 +00:00			`case RX_HANDLER_PASS:`
			`break;`
			`default:`
			`+ printk("BUG!\n");`
			`BUG();`
			`}`
			`}`