From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] bad panic "Kernel stack overflow" - demo exploit
Date: Sun, 5 Sep 2004 18:41:26 +0200 [thread overview]
Message-ID: <200409051841.26826.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200408201509.i7KF9DIF002475@ccure.user-mode-linux.org>
On Friday 20 August 2004 17:09, Jeff Dike wrote:
> blaisorblade_spam@yahoo.it said:
> > About this hunk of the patch, sorry. I tested the patch well, then I
> > added this part without testing, and understood this a lot of time
> > after. Sorry. Since CONFIG_KERNEL_STACK_ORDER is usually 2,
> > THREAD_SIZE becomes 16k (I've just realized this). So this hunk is
> > wrong. The rest works very happily.
>
> BTW, I just got rid of thread.kernel_stack since it wasn't really needed
> for anything. So that code is gone, plus some more in other places.
Yes, and I've seen you saying that the "kernel stack overflow" message is
useless because it will never run, since the stack overflowed and then
removing it altogether. Well, would you give a look at the various "kernel
stack overflow" messages appearing from various users? Simply search on the
ML archives (especially uml-user) to find them.
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-09-05 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 11:39 [uml-devel] Patch for arch/um/kernel/trap_kern.c to fix bad panic azu
2004-06-29 18:34 ` BlaisorBlade
2004-06-30 10:04 ` [uml-devel] bad panic "Kernel stack overflow" - demo exploit azu
2004-07-01 12:01 ` BlaisorBlade
2004-07-01 13:34 ` BlaisorBlade
2004-07-01 17:57 ` Alex Züpke
2004-07-01 19:33 ` BlaisorBlade
2004-07-03 18:25 ` BlaisorBlade
2004-08-17 15:40 ` BlaisorBlade
2004-08-20 15:09 ` Jeff Dike
2004-09-05 16:41 ` BlaisorBlade [this message]
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=200409051841.26826.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.