[Bug 571093] Re: [SRU] multipath + libvirtd eats away more memory over time

[Rolf Leggewie]

lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".

** Changed in: multipath-tools (Ubuntu Lucid)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/571093

Title:
  [SRU] multipath + libvirtd eats away more memory over time

Status in libvirt package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Incomplete
Status in libvirt source package in Lucid:
  Fix Released
Status in multipath-tools source package in Lucid:
  Won't Fix
Status in libvirt package in Debian:
  Fix Released

Bug description:
  libvirtd fills the memory, until the libvirtd process gets killed. This happens over a long time.
  - This server (info by ubuntu-bug) has 4GB of memory and an uptime of 27 days. Some KVM machines have been active during that period. The last 4 days before the crash, no virtual machine was running on the server, but libvirtd slowly filled memory.
  - Another server has 32 GB of memory and active virtual machines. It took a few weeks more until memory was completely filled.

  Steps to reproduce:
  - Start libvirtd
  - Wait a long time

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Apr 28 08:43:52 2010
  DistroRelease: Ubuntu 9.10
  Package: libvirt-bin 0.7.0-1ubuntu13.1
  ProcEnviron:
   LANG=C
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-server
  SourcePackage: libvirt
  Uname: Linux 2.6.31-20-server x86_64

  ======
  SRU:
   * IMPACT: If affected, libvirtd will eventually leak all memory, and OOM the system.
   * ADDRESSED: Applied patch solves two memory leaks by freeing memory on function exit conditions.
   * PATCH: As attached from Nigel Jones below.  He has also submitted this upstream as well.
   * TEST CASE: In some cases, you can reproduce this issue by running "top -p $(pidof libvirtd)" in one window, watching RES memory usage increase, while running "while true; do sudo multipath -F; sudo multipath -v4; done" in another window.  Due to a race condition (see Bug: #585027), this will sometimes not reproduce the issue by itself.  In these cases, you can "simulate" the race condition by "sudo dmsetup remove <string>", and then running the commands above.
   * REGRESSION POTENTIAL: Patch is pretty simple, clean.  Regression potential should be minimal.
  ======

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/571093/+subscriptions