Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

PM / Freezer: Remove references to TIF_FREEZE in comments

This patch removes all the references in the code about the TIF_FREEZE
flag removed by commit a320122

    freezer: make freezing() test freeze conditions in effect instead of TIF_FREEZE

There still are some references to TIF_FREEZE in
Documentation/power/freezing-of-tasks.txt, but it looks like that
documentation needs more thorough work to reflect how the new
freezer works, and hence merely removing the references to TIF_FREEZE
won't really help. So I have not touched that part in this patch.

Suggested-by: Srivatsa S. Bhat <>
Signed-off-by: Marcos Paulo de Souza <>
Signed-off-by: Rafael J. Wysocki <>
  • Loading branch information...
1 parent 8671bbc commit 37f08be11be9a7d9351fb1b9b408259519a126f3 Marcos Paulo de Souza committed with rjwysocki
Showing with 7 additions and 9 deletions.
  1. +1 −1  kernel/exit.c
  2. +3 −3 kernel/freezer.c
  3. +3 −5 kernel/power/process.c
2  kernel/exit.c
@@ -424,7 +424,7 @@ void daemonize(const char *name, ...)
- * We don't want to have TIF_FREEZE set if the system-wide hibernation
+ * We don't want to get frozen, in case system-wide hibernation
* or suspend transition begins right now.
current->flags |= (PF_NOFREEZE | PF_KTHREAD);
6 kernel/freezer.c
@@ -99,9 +99,9 @@ static void fake_signal_wake_up(struct task_struct *p)
* freeze_task - send a freeze request to given task
* @p: task to send the request to
- * If @p is freezing, the freeze request is sent by setting %TIF_FREEZE
- * flag and either sending a fake signal to it or waking it up, depending
- * on whether it has %PF_FREEZER_NOSIG set.
+ * If @p is freezing, the freeze request is sent either by sending a fake
+ * signal (if it's not a kernel thread) or waking it up (if it's a kernel
+ * thread).
* %false, if @p is not freezing or already frozen; %true, otherwise
8 kernel/power/process.c
@@ -53,11 +53,9 @@ static int try_to_freeze_tasks(bool user_only)
* It is "frozen enough". If the task does wake
* up, it will immediately call try_to_freeze.
- * Because freeze_task() goes through p's
- * scheduler lock after setting TIF_FREEZE, it's
- * guaranteed that either we see TASK_RUNNING or
- * try_to_stop() after schedule() in ptrace/signal
- * stop sees TIF_FREEZE.
+ * Because freeze_task() goes through p's scheduler lock, it's
+ * transition can't race with task state testing here.
if (!task_is_stopped_or_traced(p) &&

0 comments on commit 37f08be

Please sign in to comment.
Something went wrong with that request. Please try again.