Miroslav Benes d0807da78e 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>		2018-01-11 10:58:03 +01:00
..
callbacks.txt	livepatch: add (un)patch callbacks	2017-10-19 10:08:56 +02:00
livepatch.txt	livepatch: Remove immediate feature	2018-01-11 10:58:03 +01:00
module-elf-format.txt	Documentation: livepatch: add section about arch-specific code	2016-08-18 23:41:56 +02:00
shadow-vars.txt	livepatch: Small shadow variable documentation fixes	2017-10-02 11:55:24 +02:00