Another problem detected by running UML under Valgrind; UML implements a architecture independent version of get_wchan() in arch/um/kernel/process.c It examines each word on the stack, looking for the first one that appears to be a non-scheduler instruction pointer. Other architectures are more precise, doing things like finding the base pointer and only examining the value that should be the return address.
The UML version seems reasonable except that some values on the stack may not be initialized and will therefore have a random value, possibly a return address from a previous function call. The value of get_wchan() is exported to userspace in proc, so it's not clear to me how important it is to get this value right. -- Steve ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
