Re: [patch 1/1] openmosix/openmosix-fix-proc_pid_set_where.patch

"Matt Dew" <[email protected]> Wed, 27 Sep 2006 17:06:39 -0600
Newsgroups gmane.linux.cluster.openmosix.devel
Message-ID <[email protected]>
I've put the patches together and tested them with a script that applies
them (sans-quilt).

There are a few changes to the patches:
openmosix-kcomd-daemon-code_13.patch
  -- duplicate functions between kcom.c and kcomd.c

openmosix-kcomd-task-to-kcomd_07.patch
   -- om.where memory allocation was left out

openmosix-remove-useless-debug_17.patch
   -- extra printk that caused 'chunk failed'

openmosix-pre-kickstart_22.patch
   -- extra lines that caused 'chunk failed' error

original patches are renamed .old.


http://osource.org/openmosix/patches/series1/om-series1.tar.bz2

Ian,
A git diff is included.

On Wed, 2006-09-27 at 20:57 +0000, "Matt Dew"  wrote:
> Florian,
>  That's actually what I'm working on right now.  I've found a few
small
> things after that.
> 
> I'm hoping to put this series of patches up on my site tonight or
> tomorrow with a little shell script to correctly apply them all in
> order.
> 
> If anyone updates the git, could you post a msg to the list just to
let
> everyone know.  
> 
> thanks,
> Matt
> 
> 
> On Wed, 2006-09-27 at 19:54 +0000, Florian Delizy  wrote:
> > This patch fix the process migration. It seems some lines got lost
> from 
> > Matt's initial patch ... and the om.whereto sockaddr structure
pointer
> 
> > was left uninitialized ...
> > 
> > This patch fixes this. There is still a bug that makes the deputy
> kernel 
> > crash just after sending the process to the remote. I am
investigating
> 
> > it at the moment.
> > 
> > Matt, please can you have a look and check that there are no silly 
> > omission from your initial patch to mine ? And can you actually try
> out 
> > thoses patches over a fresh git to check for the issue I get :
> > 
> > It seems that the processor jumps at the address 0x0 just after
> sending 
> > the process. The remote process runs with no problem (I would say I 
> > guess just as long as it does not get any signal nor uses syscall
...)
> 
> > but the kernel of the deputy machine crashes badly ... I would
really 
> > appreciate some help on that, guys ...
> > 
> > Florian
> 
> 
>
-------------------------------------------------------------------------
> 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


-------------------------------------------------------------------------
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