From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [zeus][PATCH 0/9] zeus pull request - cover letter only
Date: Mon, 30 Mar 2020 23:51:23 +0800 [thread overview]
Message-ID: <cover.1585583178.git.anuj.mittal@intel.com> (raw)
Please pull these changes for zeus. Clean a-full on autobuilder.
Thanks,
Anuj
The following changes since commit c940e4b858d6be28b198770768117ecc098fa0d3:
bluez: fix CVE-2020-0556 (2020-03-16 15:49:02 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/zeus-next
Anuj Mittal (4):
icu: fix CVE-2020-10531
screen: fix CVE-2020-9366
e2fsprogs: fix CVE-2019-5188
e2fsprogs: backport upstream patch
Bruce Ashfield (1):
linux-yocto/4.19: update to v4.19.107
Chee Yang Lee (1):
wic/direct: reserve 2 sector for extended partition
Julius Hemanth Pitti (1):
nfs-utils: Disable statx if using glibc emulation
Ross Burton (1):
sanity: check for more bits of Python
Tom Hochstein (1):
security_flags.inc: fix flags missing from SDK toolchain
meta/classes/sanity.bbclass | 12 +-
meta/conf/distro/include/security_flags.inc | 2 +
...sable-statx-if-using-glibc-emulation.patch | 34 +++++
.../nfs-utils/nfs-utils_2.4.1.bb | 1 +
...-t-try-to-rehash-a-deleted-directory.patch | 49 +++++++
.../e2fsprogs/e2fsprogs/CVE-2019-5188.patch | 57 ++++++++
...fix-use-after-free-in-calculate_tree.patch | 76 +++++++++++
.../e2fsprogs/e2fsprogs_1.45.3.bb | 3 +
.../screen/screen/CVE-2020-9366.patch | 48 +++++++
meta/recipes-extended/screen/screen_4.6.2.bb | 1 +
.../linux/linux-yocto-rt_4.19.bb | 6 +-
.../linux/linux-yocto-tiny_4.19.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_4.19.bb | 20 +--
.../icu/icu/CVE-2020-10531.patch | 122 ++++++++++++++++++
meta/recipes-support/icu/icu_64.2.bb | 1 +
scripts/lib/wic/plugins/imager/direct.py | 6 +-
16 files changed, 421 insertions(+), 25 deletions(-)
create mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/0001-Disable-statx-if-using-glibc-emulation.patch
create mode 100644 meta/recipes-devtools/e2fsprogs/e2fsprogs/0001-e2fsck-don-t-try-to-rehash-a-deleted-directory.patch
create mode 100644 meta/recipes-devtools/e2fsprogs/e2fsprogs/CVE-2019-5188.patch
create mode 100644 meta/recipes-devtools/e2fsprogs/e2fsprogs/e2fsck-fix-use-after-free-in-calculate_tree.patch
create mode 100644 meta/recipes-extended/screen/screen/CVE-2020-9366.patch
create mode 100644 meta/recipes-support/icu/icu/CVE-2020-10531.patch
--
2.25.1
reply other threads:[~2020-03-30 15:51 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.1585583178.git.anuj.mittal@intel.com \
--to=anuj.mittal@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.