kpatch/.gitignore

*.o
*.o.cmd
*.o.d
*.ko
*.ko.cmd
*.mod.c
*.swp
.tmp_versions
Module.symvers
kpatch-build/lookup.o
kpatch-build/lookup
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`
gitignore *.o.d When the core module compilation fails, a kmod/core/.core.o.d file appears. 2014-04-28 21:09:04 +00:00			`*.o.d`
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			`*.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`
merge add-patches-section functionality into create-obj-diff In preparation for dynamic symbol linking, the symbol lookup logic is going to move into create-diff-obj anyway. We might as well minimize the code duplication and pull this into create-diff-obj. This avoids having to re-parse the ELF file modify it in-place. Signed-off-by: Seth Jennings <sjenning@redhat.com> Conflicts: kpatch-build/kpatch-build 2014-05-14 20:43:58 +00:00			`kpatch-build/lookup.o`
			`kpatch-build/lookup`
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/create-diff-object`
Revert #186 (add dynamic symbol linking support) We merged PR #186 a little too hastily. It seg faults with the new parainstructions-section.patch in the integration test suite. Reverting it for now until we get it figured out. This reverts commit e1177e3a03d28858181d577745b159cd7ba694b0. This reverts commit 880e271841177551ccf20e7c758a666ad813c196. This reverts commit 2de5f6cbfb43ca4db2ecdb62770647f9d7c8ee6b. This reverts commit 38b7ac74ad9d1eafac17721af5841b184dfda00d. This reverts commit 108cd9f95ebfb69d81ef0a6ea41de23212d9cfc1. 2014-05-15 22:17:29 +00:00			`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`