Home Home > GIT Browse
diff options
authorMiroslav Benes <mbenes@suse.cz>2015-05-20 16:32:17 +0200
committerMiroslav Benes <mbenes@suse.cz>2015-05-20 16:32:17 +0200
commit830e1a35578506ad9310604fe7e3a4c02bdbb770 (patch)
parenta55e02359843d4400c30b830e8f29028a18f9c4c (diff)
Set immediate flag to false
Using immediate set to true can lead to BUGs and oopses when downgrading, reverting or applying replace_all patches. There is no way how to find out if there is a process in the old code which is being removed. The module would be put, removed and the process will crash. The consistency model guarantees that there is no one in the old code when the finalization ends. Thus use it for all case to be safe. Signed-off-by: Miroslav Benes <mbenes@suse.cz>
1 files changed, 1 insertions, 1 deletions
diff --git a/kgr_patch_main.c b/kgr_patch_main.c
index e4ca9c5..35e9994 100644
--- a/kgr_patch_main.c
+++ b/kgr_patch_main.c
@@ -8,7 +8,7 @@ static struct kgr_patch patch = {
.name = "kgraft-patch-@@RPMRELEASE@@",
.owner = THIS_MODULE,
.replace_all = true,
- .immediate = true,
+ .immediate = false,
.patches = {
KGR_PATCH(SyS_newuname, kgr_sys_newuname, true),