From: Jeff Dike <jdike@addtoit.com>
To: "D. Bahi" <dbahi@enterasys.com>
Cc: uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] UML startup -- segfault with no mm
Date: Mon, 28 Feb 2005 14:34:27 -0500 [thread overview]
Message-ID: <200502281934.j1SJYRMY003256@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 24 Feb 2005 13:38:05 EST." <421E1F0D.4040108@enterasys.com>
dbahi@enterasys.com said:
> actually - 2.4.26-3um looks like this already.
Yeah, if I had spent a bit more time looking at the stack, I would have noticed
that the symptom was wrong for that patch. What's happening is that you are
taking a timer interrupt while on the initial process stack, which can't be
allowed because interrupts should only happen on a kernel stack.
Make sure your initial_thread_cb_skas (in arch/um/kernel/skas/process.c)
blocks signals like so:
block_signals();
if(sigsetjmp(here, 1) == 0)
siglongjmp(initial_jmpbuf, 2);
unblock_signals();
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
next prev parent reply other threads:[~2005-02-28 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 4:36 [uml-devel] UML startup -- segfault with no mm D. Bahi
2005-02-24 17:36 ` Jeff Dike
2005-02-24 16:09 ` D. Bahi
2005-02-24 18:38 ` D. Bahi
2005-02-28 19:34 ` Jeff Dike [this message]
2005-02-28 18:48 ` D. Bahi
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=200502281934.j1SJYRMY003256@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=dbahi@enterasys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox