Skip to content

ci: suppress valgrind failure on Debian related to the xz backdoor

Íñigo Huguet requested to merge ih/valgrind-lzma into main

Summary

Suppress a Valgrind failure not related to our code that is making the CI to be red in Debian testing and sid.

Purpose

On Debian sid and testing we get these Valgrind failures that are not related to our code, but to the xz backdoor that has been discovered.

Supress them. If we don't do it, we'll need to ignore the red state and it might cover other problems different to this one.

The suppression contains the version of liblzma so I hope that it won't be used once liblzma is updated to a new (and fixed) version in Debian repos.

Valgrind logs:

 Invalid write of size 8
    at 0x508AD45: ??? (in /usr/lib/x86_64-linux-gnu/liblzma.so.5.6.0)
    by 0x506D81B: ??? (in /usr/lib/x86_64-linux-gnu/liblzma.so.5.6.0)
    by 0x6A00000006: ???
    by 0x5066FFF: ??? (in /usr/lib/x86_64-linux-gnu/liblz4.so.1.9.4)
    by 0x203A2900A5DE11FF: ???
    by 0x1FFEFFC34F: ???
    by 0x400EFAA: elf_machine_rela (dl-machine.h:300)
    by 0x400EFAA: elf_dynamic_do_Rela (do-rel.h:147)
    by 0x400EFAA: _dl_relocate_object (dl-reloc.c:301)
    by 0x52296FF: ???
    by 0x543762F: ???
    by 0x1FFEFFC2DF: ???
  Address 0x1ffeffb3f8 is on thread 1's stack
  136 bytes below stack pointer

Checklist

Please read https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/main/CONTRIBUTING.md before opening the merge request. In particular, check that:

  • the subject for all commits is concise and explicative
  • the message for all commits explains the reason for the change
  • the source is properly formatted
  • any relevant documentation is up to date
  • you have added unit tests if applicable
  • the NEWS file is updated when the change deserves to be mentioned, for example for new features, behavior changes, API deprecations, etc.

Merge request reports