From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
caker@linode.com, user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Fix stack corruption
Date: Wed, 12 Jan 2005 18:18:13 +0100 [thread overview]
Message-ID: <200501121818.13521.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200501121856.j0CIuMiZ003766@ccure.user-mode-linux.org>
On Wednesday 12 January 2005 19:56, Jeff Dike wrote:
> This patch fixes a long-standing problem in skas mode process creation.
So, probably, unless confirmed otherwise, the problem with CONFIG_KMOD (when
the kernel starts modprobe from a kernel thread) could be due to this bug...
however, I'm not so sure, because IIRC that problem give a verbose error
message (I think even a stack trace).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
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-12 17:16 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 [this message]
2005-01-13 23:30 ` Christopher S. Aker
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=200501121818.13521.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=caker@linode.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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.