From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11911] New: systemd v240 memory leak in systemd-journald (buildroot 2019.02 LTS affected)
Date: Fri, 24 May 2019 18:48:11 +0000 [thread overview]
Message-ID: <bug-11911-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11911
Bug ID: 11911
Summary: systemd v240 memory leak in systemd-journald
(buildroot 2019.02 LTS affected)
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jonah at sense.com
CC: buildroot at uclibc.org
Target Milestone: ---
There has been a fix to a large memory leak in systemd-journald v240. I
believe that the buildroot LTS versions is affected. Should the patch provided
in the bug report be applied to the LTS branch?
Bug report: https://github.com/systemd/systemd/issues/11502
Accepted patch: https://github.com/systemd/systemd/pull/11527
Alternatively, this fix has been incorporated into systemd v241, which has been
incorporated into buildroot's master branch already. So another solution would
be to move buildroot LTS to use systemd v241.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-05-24 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 18:48 bugzilla at busybox.net [this message]
2019-05-27 13:17 ` [Buildroot] [Bug 11911] systemd v240 memory leak in systemd-journald (buildroot 2019.02 LTS affected) bugzilla at busybox.net
2019-05-27 22:23 ` bugzilla at busybox.net
2019-05-27 22:38 ` bugzilla at busybox.net
2019-05-28 17:32 ` bugzilla at busybox.net
2019-05-30 12:58 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-11911-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox