All of lore.kernel.org
 help / color / mirror / Atom feed
From: "D. Bahi" <dbahi@enterasys.com>
To: Jeff Dike <jdike@addtoit.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 13:48:16 -0500	[thread overview]
Message-ID: <42236770.6060307@enterasys.com> (raw)
In-Reply-To: <200502281934.j1SJYRMY003256@ccure.user-mode-linux.org>

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

yep. have exactly that:

void initial_thread_cb_skas(void (*proc)(void *), void *arg)
{
    sigjmp_buf here;

    cb_proc = proc;
    cb_arg = arg;
    cb_back = &here;

    block_signals();
    if(sigsetjmp(here, 1) == 0)
        siglongjmp(initial_jmpbuf, 2);
    unblock_signals();

    cb_proc = NULL;
    cb_arg = NULL;
    cb_back = NULL;
}


Jeff Dike wrote:

>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
>
>
>

--
db


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

      reply	other threads:[~2005-02-28 18:48 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
2005-02-28 18:48       ` D. Bahi [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=42236770.6060307@enterasys.com \
    --to=dbahi@enterasys.com \
    --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.