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: Thu, 19 Feb 2004 21:06:05 -0500 [thread overview]
Message-ID: <200402200206.i1K265QH004886@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 19 Feb 2004 20:01:26 +0100." <200402192001.26102.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> By the way, would you check if this is needed in the 2.4 kernel, too?
> I've checked the 2.4.24-1 uml patch and it seems to miss that line
> (and your reason seem to apply to 2.4 too).
Yup, I think so too.
> What is more strange is that the panic happens deterministically, and
> in the same situation (same root fs and same kernel) I get it at the
> same addresses! Since what happens seem to change with each single
> kernel, but is easily repeatable, I would say that it is not a race
> condition, but something with a crazy pointer outside of the core
> code.
I'm seeing two things, which don't happen deterministically :
an exited process scheduling to itself, causing the exit.c BUG - I
don't see what prevents a TASK_ZOMBIE process from being schedulable offhand.
It doesn't seem to be dequeued from any runqueues as a result of calling exit().
a segfault in schedule() caused by there being not bits set in the
queue bitmap (except for bit 140 which I guess is there to prevent ffs from
running into nowhereland). And bit 140 doesn't refer to a valid queue, so
the task pulled of it is bogus.
> So it seems that both active.queue[140] and active.queue.nr_active
> are corrupted.
Repeating the above, it looks like #140 isn't supposed to be valid.
> However, even in expired.queue[125] there is a problem, since in the
> list there is one list_head (the one at 0xa08e40a0) whose next and
> prev pointers point to itself (i.e. that is an empty list); however
> this "empty list" can be reached by expired.queue[125].
Yup, interesting. What I would do is stick some code in that looks for
this condition (and if you can look for it being created, that's even better).
I was looking for something that seemed like an invariant being violated,
and came up empty. This looks like a good one, though. If we can figure
out what's causing it, that gets us one step closer to the bug.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-20 1:43 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
2004-02-17 7:18 ` William Stearns
2004-02-19 19:01 ` BlaisorBlade
2004-02-20 2:06 ` Jeff Dike [this message]
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=200402200206.i1K265QH004886@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