From: "Christopher S. Aker" <caker@theshore.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Fix stack corruption
Date: Thu, 13 Jan 2005 18:35:43 -0600 [thread overview]
Message-ID: <001201c4f9d0$fbde9a40$0201a8c0@hawk> (raw)
In-Reply-To: 200501140127.09333.blaisorblade@yahoo.it
> > I believe we've figured out that this is skas3 specific. Once you start
> > ping-flooding the UML, it crashes within a second.
> I wasn't able to riproduce it... I ran two instances of the above loop + a
> ping flood from the host, but it didn't crash UML, even after letting it that
> way for some minutes.
What UML version are you running? Also, can you reproduce it without Jeff's patch?
Under skas3, I can't crash my UML's using Jeff's "ls > /dev/null" method, with or
without his patch.
I've been able to reproduce my crash with two different host kernels, an older 2.6.4,
and the newest 2.6.10+skas-v7. Guest kernels that crash that I've tried include
2.6.9-bb4, 2.6.10, and 2.6.10-mm2 plus the incrementals from yesterday. Also, I
believe Frank Sorenson is also able to reproduce this crash.
Thanks,
-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-14 0:34 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
2005-01-14 0:27 ` Blaisorblade
2005-01-14 0:35 ` Christopher S. Aker [this message]
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='001201c4f9d0$fbde9a40$0201a8c0@hawk' \
--to=caker@theshore.net \
--cc=blaisorblade@yahoo.it \
--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