The jump_label_init() run in a very early stage, even before the sched_init(). So there is no chance for concurrent access of the jump label table.
Signed-off-by: Kevin Hao <haoke...@gmail.com> --- kernel/jump_label.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/jump_label.c b/kernel/jump_label.c index f7dd15d537f9..df1a7fbe7cd5 100644 --- a/kernel/jump_label.c +++ b/kernel/jump_label.c @@ -205,7 +205,6 @@ void __init jump_label_init(void) struct static_key *key = NULL; struct jump_entry *iter; - jump_label_lock(); jump_label_sort_entries(iter_start, iter_stop); for (iter = iter_start; iter < iter_stop; iter++) { @@ -229,7 +228,6 @@ void __init jump_label_init(void) #endif } static_key_initialized = true; - jump_label_unlock(); } #ifdef CONFIG_MODULES -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/