diff options
author | Tim Van Patten <timvp@google.com> | 2023-11-15 09:20:43 -0700 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2023-11-28 08:04:03 -1000 |
commit | cff5f49d433fcd0063c8be7dd08fa5bf190c6c37 (patch) | |
tree | 8254e9daea0c23693d541d13ce63ea7e58bac370 /fs/open.c | |
parent | 037266a5f7239ead1530266f7d7af153d2a867fa (diff) | |
download | linux-cff5f49d433fcd0063c8be7dd08fa5bf190c6c37.tar.gz linux-cff5f49d433fcd0063c8be7dd08fa5bf190c6c37.tar.bz2 linux-cff5f49d433fcd0063c8be7dd08fa5bf190c6c37.zip |
cgroup_freezer: cgroup_freezing: Check if not frozen
__thaw_task() was recently updated to warn if the task being thawed was
part of a freezer cgroup that is still currently freezing:
void __thaw_task(struct task_struct *p)
{
...
if (WARN_ON_ONCE(freezing(p)))
goto unlock;
This has exposed a bug in cgroup1 freezing where when CGROUP_FROZEN is
asserted, the CGROUP_FREEZING bits are not also cleared at the same
time. Meaning, when a cgroup is marked FROZEN it continues to be marked
FREEZING as well. This causes the WARNING to trigger, because
cgroup_freezing() thinks the cgroup is still freezing.
There are two ways to fix this:
1. Whenever FROZEN is set, clear FREEZING for the cgroup and all
children cgroups.
2. Update cgroup_freezing() to also verify that FROZEN is not set.
This patch implements option (2), since it's smaller and more
straightforward.
Signed-off-by: Tim Van Patten <timvp@google.com>
Tested-by: Mark Hasemeyer <markhas@chromium.org>
Fixes: f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
Cc: stable@vger.kernel.org # v6.1+
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'fs/open.c')
0 files changed, 0 insertions, 0 deletions