kpatch/.gitignore

*.o
*.o.cmd
*.ko
*.ko.cmd
*.mod.c
*.swp
.tmp_versions
Module.symvers
kpatch-build/add-patches-section
kpatch-build/create-diff-object
kpatch-build/link-vmlinux-syms
man/kpatch.1.gz
man/kpatch-build.1.gz
test/integration/test.log
It's alive... The end-to-end patching works. From object analysis to generation to runtime patching. It's still missing the scripting piece that will only take a patch and kernel source dir as input. 2013-01-15 03:46:38 +00:00			`*.o`
			`*.o.cmd`
			`*.ko`
			`*.ko.cmd`
			`*.mod.c`
incremental patching and rmmod support 2013-01-18 18:31:14 +00:00			`*.swp`
build and install core module with make Build and install the kpatch core module with make and make install, rather than building it every time with kpatch build. The only downside to this approach is that the user has to make and make install kpatch every time they get a new kernel. But this is only temporary, until the kpatch module is delivered in an RPM. 2014-02-18 04:37:07 +00:00			`.tmp_versions`
			`Module.symvers`
functional reorganization Organize the files functionally: - kmod/core: core kmod source - kmod/patch: patch kmod source - kpatch: kpatch script - kpatch-build: kpatch build script and supporting tools - contrib: distro-related files 2014-02-13 13:49:02 +00:00			`kpatch-build/add-patches-section`
			`kpatch-build/create-diff-object`
			`kpatch-build/link-vmlinux-syms`
add man .gz files to gitignore Signed-off-by: Seth Jennings <sjenning@redhat.com> 2014-03-27 21:29:14 +00:00			`man/kpatch.1.gz`
			`man/kpatch-build.1.gz`
create integration test framework This is a basic integration test framework for kpatch, which tests building, loading, and unloading patches, as well as any other related custom tests. The kpatch-test script looks for test input files in the tests/integration directory. It expects certain file naming conventions: - foo.patch - patch that should build successfully - bar-FAIL.patch - patch that should fail to build - foo-LOADED.test - executable which tests whether the foo.patch module is loaded. It will be used to test that loading/unloading the patch module works as expected. Any other .test files will be executed after all the patch modules have been built from the .patch files. They can be used for more custom tests above and beyond the simple loading and unloading tests. I just have one test here, but many more to come eventually. I'm constantly doing manual testing of patches and am planning on automating them with this framework. 2014-04-26 20:40:34 +00:00			`test/integration/test.log`