summaryrefslogtreecommitdiff
path: root/crypto/eseqiv.c
diff options
context:
space:
mode:
authorDmitry Adamushko <dmitry.adamushko@gmail.com>2008-06-30 20:22:34 +0400
committerGreg Kroah-Hartman <gregkh@suse.de>2008-07-03 07:46:15 +0400
commit0758c2f30b75419fbe5e0ec6dfc892bbc0687f57 (patch)
treefbdb9529c15c6eb24b2a15e28b3d0720d2991085 /crypto/eseqiv.c
parent1e9a615bfce7996ea4d815d45d364b47ac6a74e8 (diff)
downloadlinux-0758c2f30b75419fbe5e0ec6dfc892bbc0687f57.tar.xz
sched: fix cpu hotplug
Commit 79c537998d143b127c8c662a403c3356cb885f1c upstream the CPU hotplug problems (crashes under high-volume unplug+replug tests) seem to be related to migrate_dead_tasks(). Firstly I added traces to see all tasks being migrated with migrate_live_tasks() and migrate_dead_tasks(). On my setup the problem pops up (the one with "se == NULL" in the loop of pick_next_task_fair()) shortly after the traces indicate that some has been migrated with migrate_dead_tasks()). btw., I can reproduce it much faster now with just a plain cpu down/up loop. [disclaimer] Well, unless I'm really missing something important in this late hour [/desclaimer] pick_next_task() is not something appropriate for migrate_dead_tasks() :-) the following change seems to eliminate the problem on my setup (although, I kept it running only for a few minutes to get a few messages indicating migrate_dead_tasks() does move tasks and the system is still ok) Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'crypto/eseqiv.c')
0 files changed, 0 insertions, 0 deletions