Wednesday Triage Report (2020-09-23)

[Bryce Harrington]

On Wed, Sep 23, 2020 at 11:05:50PM -0400, Sergio Durigan Junior wrote:
> Hi,
> 
> This Wednesday I did my first triage, replacing Rafael.
> 
> The only noteworthy bug I have is this one:
> 
> - https://pad.lv/1676328 - *(Confirmed) [sssd] - sssd_be is leaking
>   memory
> 
> There has been a comment by yet another person confirming the bug.  This
> is obviously not server-next, but I don't have anything meaningful to
> reply to the user for now.  Andreas, you mentioned in the bug that you
> were going to look at the changes in 1.16 and see if anything comes up;
> do you remember doing that?  I know it's been a while, but...

The confirmation isn't really adding new info to the bug that would help
move it forward.  (Indeed, the bug was never really pinpointed down to a
specific test case or root cause - who knows if the drive-by me-too is
seeing the "same" memory leak or some other bug that also leaks.)  So,
the bug probably doesn't really need a status update from us - if we
don't have any new info a reply could just be more noise.

However, if you're feeling generous one thing I sometimes do with this
sort of bug is think about what the next action would be to move it
forward in its lifecycle.  "If you'd like to help move this bug forward,
it looks to me like it is currently blocked because ______."

>From the linked bug report it says the issue was in 1.13.4 but resolved
in 1.13.5 (git) as tested on 2016-11-30.  There was never actually a
1.13.5 release, but there are commits in the upstream 'sssd-1.13' branch
after 1.13.4 was tagged.  So, a brute force git bisection search between
the 1.13.4 tag and sssd-1.13's tip might discover the solution.

  https://github.com/SSSD/sssd/commits/sssd-1-13?after=c7636e4721cb52f1b36bf93a3f27a247f3f9231f+270&branch=sssd-1-13


Bugs that take a long time to reproduce can be a PITA to git bisect
though, and it's certainly possible the leak requires more than a single
leak fix.  Looking through the git tree I spot a number of leak fixes,
e.g. just from a few months after the release:

https://github.com/SSSD/sssd/commit/e22cbe9326073e6d42fe2118661fa6daaed8638c
https://github.com/SSSD/sssd/commit/2fb750062a665dbf318b5ffb2e53f1060e43b8dc
https://github.com/SSSD/sssd/commit/312d211e03b9f3769a0362f1767cc59792e32746

So another approach might be to just blindly cherrypick anything between
1.13.4 and 2016-11-30 11:31:50 mentioning "memory" or "leak" and throw them
in a package and stick it in a ppa for testing.  But this is now more
into bug-work than triaging, and without a reliable test case to
reproduce it, it's just stabbing in the dark.

Bryce

> As a side note, this bug:
> 
> - https://pad.lv/1872527 - *(Invalid) [qemu] - Clipboard doesn't work
>   100% of the time in Ubuntu 20.04 (in KVM guests)
> 
> has received updates recently.  I'm sure Christian is on top of it, but
> I thought it'd be worth mentioning.
> 
> Other than that, the other bugs were all being taken care of.
> 
> Thanks,
> 
> -- 
> Sergio
> GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

> -----BEGIN PGP SIGNATURE-----
> 
> iQIzBAEBCgAdFiEE6S/Qs2sU8fTY4OsvEG2hyMPLvxQFAl9sDQ4ACgkQEG2hyMPL
> vxT79RAAljRjpdCebgioJaC6JZLZcaLEonyBWwFaZoTWgfkM7nnn10bZDf6cR1CJ
> Dx3pa74RJO4rEPT12Rno5T3sFbR9nMQ3SH6ZW2pfUgIIyBzUzoy9jSknOcWyPr+j
> /r7L7bwRBE+nWPd7VPj1C62Z5d4CTMex7svRIoh7WP05lB9HEQIS9qsWrEa6pFWQ
> GcIzYN3YLfjR4pzaNrncN5spgJ/a66PL0JEER6DR/f2AuFKoNCkEm+em9Uetws1/
> Jv+hroW7XoDg5cGmWvc0YvQzmydVbP5OeElJn66YBedBohEwYTMDi/EL6Eo3gPAT
> yXW0EuLlpDVLKdMCHY6DS+Ch2pm6do+5U+uG03c8MsNSTAwNhaAvSBUafVLpUFZY
> osi2CA0Vra86NHL+Zv9dLZW4/ysyTjm+U5m2dLoOGnvCOLOovhRqThKhuMe+4trZ
> 8H2c1KmaPDYUXXomVwuSxoPUFNw92ULysd5FohKzHln7tX4xlpJNbOemNIZ1DqXF
> 0z6pKWi109IAhCcJmwf9r8EP2hUTVVmNimVNSzPZnUSNTHFr/9n7k01cF/cNr4Zt
> ozy48trnx6ztXNXLDzCkHyNC66D7iM2IeCaG8ozSPoalP+BrBukQIkepr58vXXdj
> +ltTCQqBnsSyOWAICtT+XObUqjv5IIUCITwFsGV79IeqchuOB0E=
> =PLRy
> -----END PGP SIGNATURE-----

> -- 
> ubuntu-server mailing list
> ubuntu-server at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam