Am 19.02.21 um 11:28 schrieb Robert P. J. Day:
I *may* have found the problem ... as one can read here:
https://access.redhat.com/solutions/3840481
"CVE-2019-3815 systemd: memory leak in journald-server.c introduced by
fix for CVE-2018-16864"
So as I interpret that, a memory leak introduced by that earlier CVE
had to be corrected by that later CVE. I checked the state of
systemd_230 as shipped by WRL9, and it comes with an extensive set of
patches, which includes the earlier CVE, but *not* the later one.
Hmmmmmmm ...
that one should have been fixed long ago
https://bugzilla.redhat.com/show_bug.cgi?id=1665931
but your original mail didn't talk about journald at all
-------- Weitergeleitete Nachricht --------
Betreff: Looking for known memory leaks triggered by
stress testing add/remove/up/down interfaces
Datum: Thu, 18 Feb 2021 11:48:58 -0500 (EST)
Von: Robert P. J. Day <rpjday@xxxxxxxxxxxxxx>
An: Systemd mailing list <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
A colleague has reported the following apparent issue in a fairly
old (v230) version of systemd -- this is in a Yocto Project Wind River
Linux 9 build, hence the age of the package.
As reported to me (and I'm gathering more info), the system was
being put through some "longevity testing" by repeatedly adding,
removing, activating and de-activating network interfaces. According
to the report, the result was heap space slowly but inexorably being
consumed.
While waiting for more info, I'm going to examine the commit log for
systemd from v230 moving forward to collect any commits that address
memory leaks, then peruse them more carefully to see if they might
resolve the problem.
I realize it's asking a bit for folks here to remember that far
back, but does this issue sound at all familiar? Any pointers that
might save me some time? Thanks.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
