livepatch: add locking to force and signal functions
authorMiroslav Benes <mbenes@suse.cz>
Thu, 21 Dec 2017 13:40:43 +0000 (14:40 +0100)
committerJiri Kosina <jkosina@suse.cz>
Thu, 11 Jan 2018 16:36:07 +0000 (17:36 +0100)
commit8869016d3a58cbe7c31c70f4f008a92122b271c7
tree02ebd2a73b91b135034353426d3430e3b28c7832
parentc99a2be790b07752d8cc694434d3450afd4c5a00
livepatch: add locking to force and signal functions

klp_send_signals() and klp_force_transition() do not acquire klp_mutex,
because it seemed to be superfluous. A potential race in
klp_send_signals() was harmless and there was nothing in
klp_force_transition() which needed to be synchronized. That changed
with the addition of klp_forced variable during the review process.

There is a small window now, when klp_complete_transition() does not see
klp_forced set to true while all tasks have been already transitioned to
the target state. module_put() is called and the module can be removed.

Acquire klp_mutex in sysfs callback to prevent it. Do the same for the
signal sending just to be sure. There is no real downside to that.

Fixes: c99a2be790b07 ("livepatch: force transition to finish")
Fixes: 43347d56c8d9d ("livepatch: send a fake signal to all blocking tasks")
Reported-by: Jason Baron <jbaron@akamai.com>
Signed-off-by: Miroslav Benes <mbenes@suse.cz>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
kernel/livepatch/core.c