linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS
Date: Tue, 23 Nov 2004 19:22:17 +0100	[thread overview]
Message-ID: <200411231922.17600.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <001001c4d184$ca00b9f0$0201a8c0@hawk>

On Tuesday 23 November 2004 18:49, Christopher S. Aker wrote:
> > On Monday 22 November 2004 23:23, Christopher S. Aker wrote:
> > > Hello,
> >
> > Btw, question: what about your I/O token limiter? Actively using it?
> > Could start being worked on for merge (there is at least one bug-report
> > on it by "roland" on a strange but valid test-case).
> >
> > > I thought I'd give 2.6.9-bb3 a shot, and I had a bunch of users report
> > > the accumiluation of zombies.
> >
> > What the hell! This should *not* happen. What did we (I mean developers)
> > do?
>
> Just to be clear, these were zombies *inside* UML, not on the host.
*Inside*? Well, this is *VERY* different from what we were understanding. And 
nobody checked something like that...
> I'm 
> happy to blame it on the older SKAS version.
I'm not, unless your sentence mean that you have a test server on which you 
verified this is true... and even in that case, it can mean that this bug 
shows on hosts not supporting SYSEMU (like SKAS3/2.6-v1 hosts). Which would 
be anyway a bug.

And UML *should* be happy even without SYSEMU (if not for anything else, 
because you can pass "nosysemu" to it).
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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-11-23 18:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000901c4d0e1$e7f998d0$0201a8c0@hawk>
2004-11-22 22:46 ` [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS Blaisorblade
2004-11-22 23:33   ` Christopher S. Aker
2004-11-22 23:56     ` roland
2004-11-23  7:28       ` [uml-devel] Updated token-limiter patch, was " Christopher S. Aker
2004-11-23 20:10         ` Blaisorblade
2004-11-23 14:48   ` [uml-devel] " Bodo Stroesser
2004-11-23 17:49   ` Christopher S. Aker
2004-11-23 17:53     ` dopez
2004-11-23 19:30       ` Blaisorblade
2004-11-23 18:22     ` Blaisorblade [this message]
2004-11-23 18:29       ` Christopher S. Aker
2004-11-30 18:55     ` Christopher S. Aker
2004-11-30 19:23       ` Bodo Stroesser
2004-11-30 20:59         ` Christopher S. Aker

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=200411231922.17600.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=caker@theshore.net \
    --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