> The fix is obvious: > > Index: 2.6.10/arch/um/kernel/skas/process.c > =================================================================== > --- 2.6.10.orig/arch/um/kernel/skas/process.c 2005-01-12 11:17:22.000000000 > -0500 > +++ 2.6.10/arch/um/kernel/skas/process.c 2005-01-12 11:18:03.000000000 -0500 > @@ -323,9 +323,10 @@ > block_signals(); > if(sigsetjmp(fork_buf, 1) == 0) > new_thread_proc(stack, handler); > - set_signals(flags); > > remove_sigstack(); > + > + set_signals(flags); > } > > void thread_wait(void *sw, void *fb)
Just a follow up on this for the sake of a paper trail... This doesn't fix the test-case below: http://www.theshore.net/~caker/uml/crashkit-no-console-output/ readme.txt: ---- All you need is an UML guest assigned an IP on your network, iptables, and the two files below in the same directory. Run the script, while ping-flooding the UML's IP address from the host, or another machine on your network. This script works best with a 2.6 based UML. I can recreate the crash easily using 2.6.9-linode9 (based on -bb4), also available on this website. ---- I believe we've figured out that this is skas3 specific. Once you start ping-flooding the UML, it crashes within a second. -Chris ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
