diff options
author | Uladzislau Rezki (Sony) <urezki@gmail.com> | 2024-11-13 14:00:08 +0300 |
---|---|---|
committer | Frederic Weisbecker <frederic@kernel.org> | 2024-11-16 00:23:50 +0300 |
commit | 812a1c3b9f7c36d9255f0d29d0a3d324e2f52321 (patch) | |
tree | 7c4e709316c88998e074416f84a013fb5d6d2bca /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 80e935c8c154d8fbdd85a20d89b4962662ceddd7 (diff) | |
download | linux-812a1c3b9f7c36d9255f0d29d0a3d324e2f52321.tar.xz |
rcuscale: Do a proper cleanup if kfree_scale_init() fails
A static analyzer for C, Smatch, reports and triggers below
warnings:
kernel/rcu/rcuscale.c:1215 rcu_scale_init()
warn: inconsistent returns 'global &fullstop_mutex'.
The checker complains about, we do not unlock the "fullstop_mutex"
mutex, in case of hitting below error path:
<snip>
...
if (WARN_ON_ONCE(jiffies_at_lazy_cb - jif_start < 2 * HZ)) {
pr_alert("ERROR: call_rcu() CBs are not being lazy as expected!\n");
WARN_ON_ONCE(1);
return -1;
^^^^^^^^^^
...
<snip>
it happens because "-1" is returned right away instead of
doing a proper unwinding.
Fix it by jumping to "unwind" label instead of returning -1.
Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Reviewed-by: Neeraj Upadhyay <Neeraj.Upadhyay@amd.com>
Closes: https://lore.kernel.org/rcu/ZxfTrHuEGtgnOYWp@pc636/T/
Fixes: 084e04fff160 ("rcuscale: Add laziness and kfree tests")
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions