From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Struan Bartlett <struan@praguespringpeople.org>
Subject: Re: uml-patch-2.4.27-1 not fixed Re: [uml-devel] 2.4.27 guest bug reconfirmed Re bug report [ 745826 ] run cat /dev/urandom
Date: Fri, 4 Feb 2005 06:39:20 +0100 [thread overview]
Message-ID: <200502040639.20694.blaisorblade@yahoo.it> (raw)
In-Reply-To: <419A205F.7000107@praguespringpeople.org>
On Tuesday 16 November 2004 16:44, Struan Bartlett wrote:
> I've compiled and ran the test (below) on a virgin 2.4.27 kernel patched
> with uml-patch-2.4.27-1.bz2.
>
> Result: the bug is still readily reproducible and _is not fixed_ in this
> patch.
> P.S. Jeff Dike: if CONFIG_NETFILTER=y is set in .config, the patched
> kernel fails to compile.
This one was probably just a "clean-to-fix" bug.
Ok, I have just one more clue now (not the solution yet). The first problem
was that I went searching for "scheduler fixes" from 2.6: well, I merged some
more, but without success. So, I've looked again at the infamous line 564,
and what I realized (don't ask me why I missed this last time) is that this
BUG line:
if (unlikely(in_interrupt())) {
printk("Scheduling in interrupt\n");
BUG();
}
is triggered because of a bug in the urandom driver - which you use in both
your reproducing methods. So, we are down to some bug related to code in
urandom.c; since it works in mainline, I think the problem probably lies in
code managing interrupts and / or timing (since they are related to random
numbers generation).
Btw, I just got the same panic by simply running "cat /dev/urandom"!
> >>cat /dev/urandom
> >>The devastating symptom: within 5 seconds the guest kernel has paniced
> >>and exited with the message (below) "kernel BUG at sched.c:564!".
> >>_Conclusion_
> >>
> >>If such a simple pair of commands as this causes such devastating
> >>consequences, it seems the 2.4.27 kernel sched.c line 564 needs to be
> >>taken a look at - unless, that is, Jeff Dike's recent post about
> >>uml-patch-2.4.27-1 "a nasty scheduler race fixed" addresses this bug.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-02-04 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 17:34 [uml-devel] FYI: Re bug report [ 745826 ] run cat /dev/urandom Struan Bartlett
2004-11-14 10:47 ` [uml-devel] 2.4.27 guest bug reconfirmed " Struan Bartlett
2004-11-15 17:21 ` Blaisorblade
2004-11-16 15:44 ` uml-patch-2.4.27-1 not fixed " Struan Bartlett
2005-02-04 5:39 ` Blaisorblade [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=200502040639.20694.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=struan@praguespringpeople.org \
--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