We validated that commit 38816336a5 ("node_device_conf: Don't leak
@physical_function in virNodeDeviceGetPCISRIOVCaps") [0] indeed fixes
the leak investigated. Although there are more definitely-lost memory
reports from Valgrind, they are ultimately glibc-related and given the
report was in Trusty and they are not considerable leaks (at most,
8K/24H) our focus will be to fix the PCI-related leak in all libvirt
releases.

SRU template and debdiffs will get added here soon.
Cheers,


Guilherme


[0] libvirt.org/git/?p=libvirt.git;a=commit;h=38816336a5

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: libvirt (Ubuntu Focal)
   Importance: High
     Assignee: Guilherme G. Piccoli (gpiccoli)
       Status: Confirmed

** Also affects: libvirt (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu Eoan)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Bionic)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Bionic)
     Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: libvirt (Ubuntu Eoan)
     Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Memory leak on libvirt 1.3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1844455/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to