diff options
author | Miroslav Benes <mbenes@suse.cz> | 2018-01-10 11:01:28 +0100 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2018-01-11 10:58:03 +0100 |
commit | d0807da78e11d46f18399cbf8c4028c731346766 (patch) | |
tree | 7421d9d68ae0d159c816995564984a0c0cfcc26a /Documentation/pps | |
parent | c99a2be790b07752d8cc694434d3450afd4c5a00 (diff) | |
download | linux-d0807da78e11d46f18399cbf8c4028c731346766.tar.gz linux-d0807da78e11d46f18399cbf8c4028c731346766.tar.bz2 linux-d0807da78e11d46f18399cbf8c4028c731346766.zip |
livepatch: Remove immediate feature
Immediate flag has been used to disable per-task consistency and patch
all tasks immediately. It could be useful if the patch doesn't change any
function or data semantics.
However, it causes problems on its own. The consistency problem is
currently broken with respect to immediate patches.
func a
patches 1i
2i
3
When the patch 3 is applied, only 2i function is checked (by stack
checking facility). There might be a task sleeping in 1i though. Such
task is migrated to 3, because we do not check 1i in
klp_check_stack_func() at all.
Coming atomic replace feature would be easier to implement and more
reliable without immediate.
Thus, remove immediate feature completely and save us from the problems.
Note that force feature has the similar problem. However it is
considered as a last resort. If used, administrator should not apply any
new live patches and should plan for reboot into an updated kernel.
The architectures would now need to provide HAVE_RELIABLE_STACKTRACE to
fully support livepatch.
Signed-off-by: Miroslav Benes <mbenes@suse.cz>
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/pps')
0 files changed, 0 insertions, 0 deletions