summaryrefslogtreecommitdiff
path: root/include/linux/fs_stack.h
diff options
context:
space:
mode:
authorRafael J. Wysocki <rjw@sisk.pl>2006-12-13 11:34:28 +0300
committerLinus Torvalds <torvalds@woody.osdl.org>2006-12-13 20:05:49 +0300
commit3df494a32b936aef76d893f5065f962ebd9b9437 (patch)
tree825a96b219eeb87ef7a627a2494cf4fa7cd4d03e /include/linux/fs_stack.h
parent6a2d7a955d8de6cb19ed9cd194b3c83008a22c32 (diff)
downloadlinux-3df494a32b936aef76d893f5065f962ebd9b9437.tar.xz
[PATCH] PM: Fix freezing of stopped tasks
Currently, if a task is stopped (ie. it's in the TASK_STOPPED state), it is considered by the freezer as unfreezeable. However, there may be a race between the freezer and the delivery of the continuation signal to the task resulting in the task running after we have finished freezing the other tasks. This, in turn, may lead to undesirable effects up to and including data corruption. To prevent this from happening we first need to make the freezer consider stopped tasks as freezeable. For this purpose we need to make freezeable() stop returning 0 for these tasks and we need to force them to enter the refrigerator. However, if there's no continuation signal in the meantime, the stopped tasks should remain stopped after all processes have been thawed, so we need to send an additional SIGSTOP to each of them before waking it up. Also, a stopped task that has just been woken up should first check if there's a freezing request for it and go to the refrigerator if that's the case. Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl> Acked-by: Pavel Machek <pavel@ucw.cz> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/linux/fs_stack.h')
0 files changed, 0 insertions, 0 deletions