[patch 3/4] openmosix/fix-wrong-process-wakeup.patch fix wrong wake_up

Florian Delizy <[email protected]> Thu, 16 Nov 2006 23:10:55 +0100
Newsgroups gmane.linux.cluster.openmosix.devel
Message-ID <[email protected]>
When asked to migrate, process were waken up, but they should not, since
if a process is artificially waken up too early, it may (and will probably)
crash ...

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
openMosix-devel mailing list
openMosix-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openmosix-devel
fix-wrong-process-wakeup.patch (text/x-patch, 705 B)
Subject: [patch @num@/@total@] @name@ fix wrong wake_up

When asked to migrate, process were waken up, but they should not, since
if a process is artificially waken up too early, it may (and will probably)
crash ... 


Index: linux/hpc/task.c
===================================================================
--- linux.orig/hpc/task.c	2006-11-16 22:31:55.000000000 +0100
+++ linux/hpc/task.c	2006-11-16 22:32:16.000000000 +0100
@@ -228,7 +228,8 @@
 	OMDEBUG_MIG(3, "pid %d registering process migration ?\n", p->pid);
 
 	task_set_dreqs(p, DREQ_MOVE);
-	wake_up_process(p);
+	if (task_test_dflags(p,DDEPUTY))
+		wake_up_process(p);
 	set_ti_thread_flag(p->thread_info, TIF_NEED_RESCHED);
 	return 0;
 }