From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 00/11] Pull request (cover letter only)
Date: Mon, 24 Jan 2022 12:32:24 -1000 [thread overview]
Message-ID: <cover.1643063455.git.steve@sakoman.com> (raw)
The following changes since commit 01f256bc72fb45c80b6a6c77506bc4c375965a3a:
glibc: Add fix for data races in pthread_create and TLS access (2022-01-12 04:37:31 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Bruce Ashfield (5):
linux-yocto/5.4: update to v5.4.169
linux-yocto/5.4: update to v5.4.170
linux-yocto/5.4: update to v5.4.171
linux-yocto/5.4: update to v5.4.172
kernel: introduce python3-dtschema-wrapper
Kai Kang (1):
speex: fix CVE-2020-23903
Marek Vasut (1):
Revert "weston: Use systemd notify,"
Richard Purdie (1):
lttng-tools: Add missing DEPENDS on bison-native
Steve Sakoman (3):
expat fix CVE-2022-22822 through CVE-2022-22827
expat: fix CVE-2021-45960
expat: fix CVE-2021-46143
meta/conf/distro/include/maintainers.inc | 1 +
.../expat/expat/CVE-2021-45960.patch | 65 +++++
.../expat/expat/CVE-2021-46143.patch | 43 +++
.../expat/expat/CVE-2022-22822-27.patch | 257 ++++++++++++++++++
meta/recipes-core/expat/expat_2.2.9.bb | 3 +
.../wayland/weston-init/weston-start | 12 -
.../wayland/weston-init/weston@.service | 6 -
.../weston/systemd-notify.weston-start | 9 -
.../wayland/weston/xwayland.weston-start | 3 +-
meta/recipes-graphics/wayland/weston_8.0.0.bb | 6 -
.../python3-dtschema-wrapper/dt-doc-validate | 20 ++
.../dtc/python3-dtschema-wrapper/dt-mk-schema | 20 ++
.../dtc/python3-dtschema-wrapper/dt-validate | 20 ++
.../dtc/python3-dtschema-wrapper_2021.10.bb | 17 ++
.../linux/linux-yocto-rt_5.4.bb | 6 +-
.../linux/linux-yocto-tiny_5.4.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.4.bb | 22 +-
.../lttng/lttng-tools_2.11.5.bb | 2 +-
.../speex/speex/CVE-2020-23903.patch | 30 ++
meta/recipes-multimedia/speex/speex_1.2.0.bb | 4 +-
20 files changed, 500 insertions(+), 54 deletions(-)
create mode 100644 meta/recipes-core/expat/expat/CVE-2021-45960.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2021-46143.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-22822-27.patch
delete mode 100644 meta/recipes-graphics/wayland/weston/systemd-notify.weston-start
create mode 100644 meta/recipes-kernel/dtc/python3-dtschema-wrapper/dt-doc-validate
create mode 100644 meta/recipes-kernel/dtc/python3-dtschema-wrapper/dt-mk-schema
create mode 100644 meta/recipes-kernel/dtc/python3-dtschema-wrapper/dt-validate
create mode 100644 meta/recipes-kernel/dtc/python3-dtschema-wrapper_2021.10.bb
create mode 100644 meta/recipes-multimedia/speex/speex/CVE-2020-23903.patch
--
2.25.1
next reply other threads:[~2022-01-24 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 22:32 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 14:10 [OE-core][dunfell 00/11] Pull request (cover letter only) Steve Sakoman
2022-09-30 2:38 Steve Sakoman
2022-08-21 23:03 Steve Sakoman
2022-08-12 21:11 Steve Sakoman
2022-06-03 23:30 Steve Sakoman
2022-04-20 2:42 Steve Sakoman
2022-01-18 22:23 Steve Sakoman
2021-04-22 16:04 Steve Sakoman
2020-08-07 16:39 Steve Sakoman
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.1643063455.git.steve@sakoman.com \
--to=steve@sakoman.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