public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: Jasper Spaans <jasper@spaans.ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11pre2-ac1 and previous problem
Date: Mon, 13 Nov 2000 22:16:02 +1100	[thread overview]
Message-ID: <3A0FCD72.1F4C5C46@uow.edu.au> (raw)
In-Reply-To: Your message of "Mon, 13 Nov 2000 09:58:17 BST." <20001113095816.A29077@spaans.ds9a.nl> <2002.974112299@ocs3.ocs-net>

Keith Owens wrote:
> 
> On Mon, 13 Nov 2000 09:58:17 +0100,
> Jasper Spaans <jasper@spaans.ds9a.nl> wrote:
> >All right, here's another one, this time using the oops directly from the
> >console -- this seems to give better symbols.. The 'console shuts up ...'
> >works, the oops from the other CPU didn't get put out.
> 
> Ohhhh, damn!  For NMI lockups we want the console to stay live so NMI
> detection on the other cpus can be printed.  NMI is normally caused by
> spinlock problems and it is useful to know what the other cpus are
> doing.  Andrew, do you want to have a go at fixing this?

Uh, sure - I just _love_ running fsck :)  I'm working on this stuff
at present.  That wake_up in printk() is baaaaad...

> >Will try test11-pre3 + kdb this afternoon, if it compiles.
> 
> Patch kdb-v1.5-2.4.0-test11-pre3.gz should be OK.

It would be very, very interesting to see where the other CPU is.

I can see one bug from Jasper's trace: setscheduler() does:

        spin_lock_irq(&runqueue_lock);
        read_lock(&tasklist_lock);

whereas the exit_notify->do_notify_parent->send_sig_info->wake_up_process
path does:

        write_lock_irq(&tasklist_lock);
        spin_lock_irqsave(&runqueue_lock, flags);

Death by double deadlock.  But I doubt if setscheduler() is the
source - who ever calls that?

The correct locking hierarchy is, I think:

	spin_lock(runqueue_lock)
	read/write_lock(tasklist_lock)
	read/write_unlock(tasklist_lock)
	spin_unlock(runqueue_lock)

Jasper, as a random stab in the dark you may care to try this:

--- linux-2.4.0-test11-pre4/kernel/exit.c	Sun Oct 15 01:27:46 2000
+++ linux-akpm/kernel/exit.c	Mon Nov 13 22:05:37 2000
@@ -381,8 +381,10 @@
 	 *	jobs, send them a SIGHUP and then a SIGCONT.  (POSIX 3.2.2.2)
 	 */
 
-	write_lock_irq(&tasklist_lock);
+	read_lock_irq(&tasklist_lock);
 	do_notify_parent(current, current->exit_signal);
+	read_unlock_irq(&tasklist_lock);
+	write_lock_irq(&tasklist_lock);
 	while (current->p_cptr != NULL) {
 		p = current->p_cptr;
 		current->p_cptr = p->p_osptr;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-13 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 17:17 2.4.0-test11pre2-ac1 and previous problem Pawe³ Kot
2000-11-10 17:30 ` Rik van Riel
2000-11-10 17:36   ` Pawe³ Kot
2000-11-11  0:25 ` Andrew Morton
2000-11-11 15:27   ` Jasper Spaans
2000-11-12  1:32     ` Andrew Morton
2000-11-12  2:27       ` Keith Owens
2000-11-13  8:58         ` Jasper Spaans
2000-11-13 10:44           ` Keith Owens
2000-11-13 11:16             ` Andrew Morton [this message]
2000-11-13 12:11           ` Andrew Morton

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=3A0FCD72.1F4C5C46@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=jasper@spaans.ds9a.nl \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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