linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>
Subject: Re: [uml-devel] Re: Diagnosed and repeatable kernel mode panic in schedule() for 2.6!
Date: Mon, 16 Feb 2004 23:46:30 -0500	[thread overview]
Message-ID: <200402170446.i1H4kUsq026113@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 16 Feb 2004 20:25:24 +0100." <200402162025.24853.blaisorblade_spam@yahoo.it>

blaisorblade_spam@yahoo.it said:
> while /bin/true ; do /bin/true ; done 

This turned out to be slightly subtle.  It was exposed by the 
longjmp -> siglongjmp change.  New processes were created with signals 
enabled, so siglongjmp to a new process context re-enabled signals in the
middle of the context switch.

Try the patch below - it seems to fix things for me.

				Jeff


--- 1.9/arch/um/kernel/skas/process_kern.c      Thu Jan  8 07:43:01 2004
+++ edited/arch/um/kernel/skas/process_kern.c   Sun Feb 15 10:42:31 2004
@@ -76,6 +76,7 @@
 
 void new_thread_proc(void *stack, void (*handler)(int sig))
 {
+       local_irq_disable();
        init_new_thread_stack(stack, handler);
        os_usr1_process(os_getpid());
 }



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&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

  parent reply	other threads:[~2004-02-17  4:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 18:50 [uml-devel] Diagnosed and repeatable kernel mode panic in schedule() for 2.6! BlaisorBlade
2004-02-16  9:53 ` [uml-devel] " Ingo Molnar
2004-02-16 19:25   ` BlaisorBlade
2004-02-16 19:27     ` Ingo Molnar
2004-02-17  0:52       ` Jeff Dike
2004-02-17  4:46     ` Jeff Dike [this message]
2004-02-17  7:18       ` William Stearns
2004-02-19 19:01       ` BlaisorBlade
2004-02-20  2:06         ` Jeff Dike
2004-02-20  7:48           ` Ingo Molnar
2004-02-17 15:56   ` BlaisorBlade
2004-02-18 21:15     ` Jeff Dike
2004-02-19 18:15       ` 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=200402170446.i1H4kUsq026113@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=mingo@elte.hu \
    --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