From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/13] Sumo patch review
Date: Mon, 18 Mar 2019 19:13:53 -0700 [thread overview]
Message-ID: <cover.1552960566.git.akuster808@gmail.com> (raw)
Responses should be made by Wed March 20th 21:00:00 UTC 2019
The following changes since commit b28f5672ab55ea303727e9f03bc594c7774d597e:
bitbake: COW: Fix StopIteration warning (2019-03-13 14:38:56 -0700)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib stable/sumo-next
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stable/sumo-next
Bruce Ashfield (1):
linux-yocto/4.14: configuration cleanups
Chen Qi (2):
systemd: fix CVE-2018-15686
systemd: fix CVE-2018-15688
George McCollister (5):
systemd: fix CVE-2018-15687
systemd: Security fix CVE-2018-16864
systemd: Security fix CVE-2018-16865
systemd: fix CVE-2018-6954
systemd: fix CVE-2019-6454
Marcus Cooper (1):
systemd: Security fix CVE-2018-16866
Mingli Yu (1):
logrotate.py: restore /etc/logrotate.d/wtmp
ROGEZ Matthieu (1):
systemd: Fix typo in root home variable.
Richard Purdie (1):
oeqa/runtime/dnf: Fix test error when static libs are enabled
Stefan Agner (1):
run-postinsts: for dpkg/opkg, do not rely on /etc/*-postinsts
meta/lib/oeqa/runtime/cases/dnf.py | 2 +-
meta/lib/oeqa/runtime/cases/logrotate.py | 6 +-
...sive-let-s-rework-the-recursive-logic-to-.patch | 252 +++
...eserializing-state-always-use-read_line-L.patch | 250 +++
...sure-we-have-enough-space-for-the-DHCP6-o.patch | 39 +
...n-t-resolve-pathnames-when-traversing-rec.patch | 643 +++++++
.../systemd/systemd/0002-Make-tmpfiles-safe.patch | 1828 ++++++++++++++++++++
...-not-store-the-iovec-entry-for-process-co.patch | 193 +++
...ld-set-a-limit-on-the-number-of-fields-1k.patch | 60 +
...ote-set-a-limit-on-the-number-of-fields-i.patch | 79 +
...nal-fix-out-of-bounds-read-CVE-2018-16866.patch | 49 +
.../systemd/systemd/CVE-2019-6454.patch | 210 +++
...e-receive-an-invalid-dbus-message-ignore-.patch | 61 +
meta/recipes-core/systemd/systemd_237.bb | 13 +-
.../run-postinsts/run-postinsts/run-postinsts | 21 +-
.../run-postinsts/run-postinsts.service | 1 -
meta/recipes-kernel/linux/linux-yocto-rt_4.14.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_4.14.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_4.14.bb | 2 +-
19 files changed, 3697 insertions(+), 16 deletions(-)
create mode 100644 meta/recipes-core/systemd/systemd/0001-chown-recursive-let-s-rework-the-recursive-logic-to-.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-core-when-deserializing-state-always-use-read_line-L.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
create mode 100644 meta/recipes-core/systemd/systemd/0001-tmpfiles-don-t-resolve-pathnames-when-traversing-rec.patch
create mode 100644 meta/recipes-core/systemd/systemd/0002-Make-tmpfiles-safe.patch
create mode 100644 meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
create mode 100644 meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields-1k.patch
create mode 100644 meta/recipes-core/systemd/systemd/0026-journal-remote-set-a-limit-on-the-number-of-fields-i.patch
create mode 100644 meta/recipes-core/systemd/systemd/0027-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
create mode 100644 meta/recipes-core/systemd/systemd/CVE-2019-6454.patch
create mode 100644 meta/recipes-core/systemd/systemd/sd-bus-if-we-receive-an-invalid-dbus-message-ignore-.patch
--
2.7.4
reply other threads:[~2019-03-19 2:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1552960566.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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