Loading
static_call: Replace pointless WARN_ON() in static_call_module_notify()
stable inclusion from stable-v6.6.55 commit e67534bd31d79952b50e791e92adf0b3e6c13b8c category: bugfix bugzilla: https://gitee.com/src-openeuler/kernel/issues/IAYRDC Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e67534bd31d79952b50e791e92adf0b3e6c13b8c -------------------------------- [ Upstream commit fe513c2ef0a172a58f158e2e70465c4317f0a9a2 ] static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn(). Fixes: 9183c3f9 ("static_call: Add inline static call infrastructure") Signed-off-by:Thomas Gleixner <tglx@linutronix.de> Signed-off-by:
Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lkml.kernel.org/r/8734mf7pmb.ffs@tglx Signed-off-by:
Sasha Levin <sashal@kernel.org> Signed-off-by:
Liao Chen <liaochen4@huawei.com>