From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 00/20] Pull request
Date: Fri, 1 Apr 2022 10:20:07 +0800 [thread overview]
Message-ID: <cover.1648779491.git.anuj.mittal@intel.com> (raw)
The following changes since commit bcef80623f015c006778edee5cf40dad063e51db:
wic: Use custom kernel path if provided (2022-03-15 23:00:09 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Alexander Kanavin (1):
mobile-broadband-provider-info: upgrade 20201225 -> 20210805
Anuj Mittal (1):
lttng-modules: upgrade 2.12.7 -> 2.12.8
Bruce Ashfield (5):
linux-yocto: nohz_full boot arg fix
linux-yocto/5.10: split vtpm for more granular inclusion
linux-yocto/5.10: cfg/debug: add configs for kcsan
linux-yocto-rt/5.10: update to -rt61
linux-yocto/5.10: update to v5.10.107
Changhyeok Bae (1):
mobile-broadband-provider-info: upgrade 20210805 -> 20220315
Chee Yang Lee (2):
webkitgtk : update to 2.30.6
go: update to 1.16.15
Joe Slater (2):
libxml2: Fix CVE-2022-23308
zip: modify when match.S is built
Li Wang (1):
flac: fix CVE-2021-0561
Mingli Yu (2):
epiphany: fix CVEs
python3-numpy: fix CVE-2021-41496
Minjae Kim (2):
gnu-config: update SRC_URI
virglrenderer: update SRC_URI
Ovidiu Panait (1):
openssl: upgrade 1.1.1l -> 1.1.1n
Ross Burton (1):
zlib: backport the fix for CVE-2018-25032
wangmy (1):
linux-firmware: upgrade 20220209 -> 20220310
.../mobile-broadband-provider-info_git.bb | 7 +-
.../{openssl_1.1.1l.bb => openssl_1.1.1n.bb} | 3 +-
.../CVE-2022-23308-fix-regression.patch | 99 +++
.../libxml/libxml2/CVE-2022-23308.patch | 209 ++++++
meta/recipes-core/libxml/libxml2_2.9.10.bb | 2 +
.../zlib/zlib/CVE-2018-25032.patch | 347 +++++++++
meta/recipes-core/zlib/zlib_1.2.11.bb | 1 +
.../gnu-config/gnu-config_git.bb | 2 +-
.../go/{go-1.16.14.inc => go-1.16.15.inc} | 4 +-
...1.16.14.bb => go-binary-native_1.16.15.bb} | 4 +-
....16.14.bb => go-cross-canadian_1.16.15.bb} | 0
...o-cross_1.16.14.bb => go-cross_1.16.15.bb} | 0
...ssdk_1.16.14.bb => go-crosssdk_1.16.15.bb} | 0
...native_1.16.14.bb => go-native_1.16.15.bb} | 0
...ntime_1.16.14.bb => go-runtime_1.16.15.bb} | 0
.../go/{go_1.16.14.bb => go_1.16.15.bb} | 0
.../python-numpy/files/CVE-2021-41496.patch | 64 ++
.../python-numpy/python3-numpy_1.20.1.bb | 1 +
.../0001-configure-use-correct-CPP.patch | 47 ++
...002-configure-support-PIC-code-build.patch | 34 +
meta/recipes-extended/zip/zip_3.0.bb | 2 +
.../recipes-gnome/epiphany/epiphany_3.38.2.bb | 1 +
.../files/encode-untrusted-data.patch | 707 ++++++++++++++++++
.../virglrenderer/virglrenderer_0.8.2.bb | 2 +-
...20220209.bb => linux-firmware_20220310.bb} | 6 +-
.../linux/linux-yocto-rt_5.10.bb | 6 +-
.../linux/linux-yocto-tiny_5.10.bb | 8 +-
meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 +-
...ules_2.12.7.bb => lttng-modules_2.12.8.bb} | 2 +-
.../flac/flac/CVE-2021-0561.patch | 41 +
meta/recipes-multimedia/flac/flac_1.3.3.bb | 1 +
...ebkitgtk_2.30.5.bb => webkitgtk_2.30.6.bb} | 2 +-
32 files changed, 1592 insertions(+), 34 deletions(-)
rename meta/recipes-connectivity/openssl/{openssl_1.1.1l.bb => openssl_1.1.1n.bb} (98%)
create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-23308-fix-regression.patch
create mode 100644 meta/recipes-core/libxml/libxml2/CVE-2022-23308.patch
create mode 100644 meta/recipes-core/zlib/zlib/CVE-2018-25032.patch
rename meta/recipes-devtools/go/{go-1.16.14.inc => go-1.16.15.inc} (91%)
rename meta/recipes-devtools/go/{go-binary-native_1.16.14.bb => go-binary-native_1.16.15.bb} (83%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.16.14.bb => go-cross-canadian_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.16.14.bb => go-cross_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.16.14.bb => go-crosssdk_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.16.14.bb => go-native_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go-runtime_1.16.14.bb => go-runtime_1.16.15.bb} (100%)
rename meta/recipes-devtools/go/{go_1.16.14.bb => go_1.16.15.bb} (100%)
create mode 100644 meta/recipes-devtools/python-numpy/files/CVE-2021-41496.patch
create mode 100644 meta/recipes-extended/zip/zip-3.0/0001-configure-use-correct-CPP.patch
create mode 100644 meta/recipes-extended/zip/zip-3.0/0002-configure-support-PIC-code-build.patch
create mode 100644 meta/recipes-gnome/epiphany/files/encode-untrusted-data.patch
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20220209.bb => linux-firmware_20220310.bb} (99%)
rename meta/recipes-kernel/lttng/{lttng-modules_2.12.7.bb => lttng-modules_2.12.8.bb} (94%)
create mode 100644 meta/recipes-multimedia/flac/flac/CVE-2021-0561.patch
rename meta/recipes-sato/webkit/{webkitgtk_2.30.5.bb => webkitgtk_2.30.6.bb} (98%)
--
2.35.1
next reply other threads:[~2022-04-01 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 2:20 Anuj Mittal [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-15 6:37 [hardknott][PATCH 00/20] Pull request Anuj Mittal
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.1648779491.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.