From: "Christopher S. Aker" <caker@theshore.net>
To: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] Fix stack corruption
Date: Thu, 13 Jan 2005 17:30:28 -0600 [thread overview]
Message-ID: <002001c4f9c7$de282ec0$0201a8c0@hawk> (raw)
In-Reply-To: 200501121856.j0CIuMiZ003766@ccure.user-mode-linux.org
> 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
next prev parent reply other threads:[~2005-01-13 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 18:56 [uml-devel] [PATCH] Fix stack corruption Jeff Dike
2005-01-12 17:18 ` Blaisorblade
2005-01-13 23:30 ` Christopher S. Aker [this message]
2005-01-14 0:27 ` Blaisorblade
2005-01-14 0:35 ` Christopher S. Aker
2005-01-14 0:42 ` Blaisorblade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002001c4f9c7$de282ec0$0201a8c0@hawk' \
--to=caker@theshore.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox