Comment 4 for bug 2024114

Hi Paride, thanks for the quick response. Please find answers in line below:

> 1. Can you confirm you have access to the right hardware and will perform the SRU verification?
Yes, this is possible.

> 2. The DEP-3 headers of the patch have "Origin: upstream", but the bug description says that "The backport is derived from an upstream fix". In DEP-3 language "backport" means that an upstream patch/commit had to be modified to cleanly apply. Is this a clean cherry-pick (Origin: upstream) or a backport (Origin: backport)?
Sorry for the ambiguity. There was no modification to the actual code, however the line numbers where code was inserted and removed have some offset due to new code in the file (ie. quilt pushed correctly with fuzz). I assume this means it is technically a backport? Let me know and I will update the patch accordingly.

> 3. By checking the libvirt versions looks like this bug is Fix Released in >= Kinetic. Can you please confirm this?
Upstream, the fix was backported to 8.10+. I double checked and the fix is not present in kinetic, but is in lunar. (Note, focal does not exhibit this issue). I will update the bug and prepare a patch for kinetic accordingly.

> 4. Was the fix already tested by building the package in a PPA?
Yes this has been tested using a PPA and fixes the particular leak we observed.