From: Leszek Urbanski <tygrys@moo.pl>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Ryan Harper <ryanh@us.ibm.com>, kvm@vger.kernel.org
Subject: Re: Huge memory leak in virtio, see kvm-Bugs-2989366
Date: Wed, 21 Apr 2010 15:29:37 +0200 [thread overview]
Message-ID: <20100421132937.GA22350@moo.pl> (raw)
In-Reply-To: <4BCE9654.2030604@msgid.tls.msk.ru>
<4BCE9654.2030604@msgid.tls.msk.ru>; from Michael Tokarev on Wed, Apr 21, 2010 at 10:08:20 +0400
>
> There are only a few guests which are affected. So far it is not
> really clear what differs them from others: a reinstall of a new
> guest with the same components and doing same functions will not
> necessary show the leak.
I checked further and I can reproduce it on every guest with a simple:
while true ; do dd if=/dev/urandom of=file bs=10M count=200 ; cat file > /dev/null ; done
It will leak slowly.
--
Leszek "Tygrys" Urbanski, SCSA, SCNA
"Unix-to-Unix Copy Program;" said PDP-1. "You will never find a more
wretched hive of bugs and flamers. We must be cautious." -- DECWARS
http://cygnus.moo.pl/ -- Cygnus High Altitude Balloon
next prev parent reply other threads:[~2010-04-21 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 22:29 Huge memory leak in virtio, see kvm-Bugs-2989366 Leszek Urbanski
2010-04-20 22:51 ` Alexander Graf
2010-04-21 7:53 ` Leszek Urbanski
2010-04-21 8:25 ` Avi Kivity
2010-04-21 1:58 ` Ryan Harper
2010-04-21 6:08 ` Michael Tokarev
2010-04-21 13:29 ` Leszek Urbanski [this message]
2010-04-21 18:39 ` Stefan Hajnoczi
2010-04-21 14:32 ` Ryan Harper
2010-04-21 18:27 ` [PATCH] block: Free iovec arrays allocated by multiwrite_merge() Stefan Hajnoczi
2010-04-21 18:35 ` Ryan Harper
2010-04-21 18:43 ` Brian Jackson
2010-04-21 19:59 ` Leszek Urbanski
2010-04-21 20:03 ` Ryan Harper
2010-04-21 20:13 ` Leszek Urbanski
2010-04-25 12:36 ` Avi Kivity
2010-04-25 13:27 ` Stefan Hajnoczi
2010-04-25 13:35 ` Avi Kivity
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=20100421132937.GA22350@moo.pl \
--to=tygrys@moo.pl \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=ryanh@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.