static_call: Fix static_call_text_reserved() vs __init
authorPeter Zijlstra <peterz@infradead.org>
Mon, 28 Jun 2021 11:24:11 +0000 (13:24 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 20 Jul 2021 14:05:58 +0000 (16:05 +0200)
commit53c5c2496fc9953ca1e67d3435f7d3f111da86d3
treeed72b025cf71ce960ca264c6c01fc4bafeace4dd
parent59ae35884c5e6a90e9659f43dda20b0167fc9f8d
static_call: Fix static_call_text_reserved() vs __init

[ Upstream commit 2bee6d16e4379326b1eea454e68c98b17456769e ]

It turns out that static_call_text_reserved() was reporting __init
text as being reserved past the time when the __init text was freed
and re-used.

This is mostly harmless and will at worst result in refusing a kprobe.

Fixes: 6333e8f73b83 ("static_call: Avoid kprobes on inline static_call()s")
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
Link: https://lore.kernel.org/r/20210628113045.106211657@infradead.org
Signed-off-by: Sasha Levin <sashal@kernel.org>
kernel/static_call.c