From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][kirkstone 00/35] Pull request (cover letter only)
Date: Wed, 23 Nov 2022 04:18:06 -1000 [thread overview]
Message-ID: <cover.1669212990.git.steve@sakoman.com> (raw)
The following changes since commit 3243b069db7629d15e4b8c25b4133f824d18520c:
qemu: add io_uring PACKAGECONFIG (2022-11-10 07:13:46 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next
Alex Kiernan (1):
cargo_common.bbclass: Fix typos
Alexander Kanavin (6):
lttng-tools: submit determinism.patch upstream
groff: submit patches upstream
tcl: correct patch status
kea: submit patch upstream
ovmf: correct patches status
libffi: submit patch upstream
Diego Sueiro (1):
kernel.bbclass: Include randstruct seed assets in
STAGING_KERNEL_BUILDDIR
Hitendra Prajapati (1):
systemd: CVE-2022-3821 Fix buffer overrun
Jose Quaresma (1):
archiver: avoid using machine variable as it breaks multiconfig
Kai Kang (1):
libuv: fixup SRC_URI
Leon Anavi (1):
get_module_deps3.py: Check attribute '__file__'
Marek Vasut (1):
bluez5: Point hciattach bcm43xx firmware search path to /lib/firmware
Nathan Rossi (4):
oeqa/selftest/lic_checksum: Cleanup changes to emptytest include
oeqa/selftest/minidebuginfo: Create selftest for minidebuginfo
glibc-locale: Do not INHIBIT_DEFAULT_DEPS
package: Fix handling of minidebuginfo with newer binutils
Niko Mauno (1):
systemd: Consider PACKAGECONFIG in RRECOMMENDS
Richard Purdie (6):
lttng-modules: upgrade 2.13.5 -> 2.13.7
bitbake.conf: Drop export of SOURCE_DATE_EPOCH_FALLBACK
gcc-shared-source: Fix source date epoch handling
gcc-source: Fix gengtypes race
gcc-source: Drop gengtype manipulation
gcc-source: Ensure deploy_source_date_epoch sstate hash doesn't change
Ross Burton (1):
expat: upgrade to 2.5.0
Sergei Zhmylev (1):
wic: make ext2/3/4 images reproducible
Steve Sakoman (1):
Revert "expat: backport the fix for CVE-2022-43680"
Wang Mingyu (3):
bind: upgrade 9.18.7 -> 9.18.8
socat: upgrade 1.7.4.3 -> 1.7.4.4
libxcrypt: upgrade 4.4.28 -> 4.4.30
Xiangyu Chen (5):
dbus: fix CVE-2022-42010 Check brackets in signature nest correctly
dbus: fix CVE-2022-42011 dbus-daemon can be crashed by messages with
array length inconsistent with element type
dbus: fix CVE-2022-42012 dbus-marshal-byteswap: Byte-swap Unix fd
indexes if needed
lttng-tools: Upgrade 2.13.4 -> 2.13.8
sudo: upgrade 1.9.10 -> sudo 1.9.12p1
meta/classes/archiver.bbclass | 2 +-
meta/classes/cargo_common.bbclass | 4 +-
meta/classes/kernel.bbclass | 16 +++
meta/classes/package.bbclass | 21 +++-
meta/conf/bitbake.conf | 2 +-
meta/lib/oeqa/selftest/cases/lic_checksum.py | 2 +
meta/lib/oeqa/selftest/cases/minidebuginfo.py | 49 ++++++++
...1-avoid-start-failure-with-bind-user.patch | 0
...d-V-and-start-log-hide-build-options.patch | 0
...ching-for-json-headers-searches-sysr.patch | 0
.../bind/{bind-9.18.7 => bind-9.18.8}/bind9 | 0
.../{bind-9.18.7 => bind-9.18.8}/conf.patch | 0
.../generate-rndc-key.sh | 0
...t.d-add-support-for-read-only-rootfs.patch | 0
.../make-etc-initd-bind-stop-work.patch | 0
.../named.service | 0
.../bind/{bind_9.18.7.bb => bind_9.18.8.bb} | 2 +-
meta/recipes-connectivity/bluez5/bluez5.inc | 2 +
.../kea/files/fix-multilib-conflict.patch | 2 +-
.../libuv/libuv_1.44.2.bb | 2 +-
...ck-getprotobynumber_r-with-AC_TRY_LI.patch | 35 ------
.../{socat_1.7.4.3.bb => socat_1.7.4.4.bb} | 6 +-
...eswap-Byte-swap-Unix-fd-indexes-if-n.patch | 76 +++++++++++
...idate-Check-brackets-in-signature-ne.patch | 119 ++++++++++++++++++
...idate-Validate-length-of-arrays-of-f.patch | 61 +++++++++
meta/recipes-core/dbus/dbus_1.14.0.bb | 3 +
.../expat/expat/CVE-2022-43680.patch | 33 -----
.../expat/{expat_2.4.9.bb => expat_2.5.0.bb} | 3 +-
meta/recipes-core/glibc/glibc-locale.inc | 11 +-
...t_4.4.28.bb => libxcrypt-compat_4.4.30.bb} | 0
meta/recipes-core/libxcrypt/libxcrypt.inc | 2 +-
...ibxcrypt_4.4.28.bb => libxcrypt_4.4.30.bb} | 0
...ovmf-update-path-to-native-BaseTools.patch | 2 +-
...ile-adjust-to-build-in-under-bitbake.patch | 7 +-
.../systemd/systemd/CVE-2022-3821.patch | 45 +++++++
meta/recipes-core/systemd/systemd_250.5.bb | 5 +-
.../gcc/gcc-shared-source.inc | 10 ++
meta/recipes-devtools/gcc/gcc-source.inc | 9 +-
.../python/python3/get_module_deps3.py | 2 +-
.../tcl/fix_non_native_build_issue.patch | 2 +-
...001-Make-manpages-mulitlib-identical.patch | 2 +-
...001-replace-perl-w-with-use-warnings.patch | 2 +-
meta/recipes-extended/sudo/sudo.inc | 2 +-
.../sudo/{sudo_1.9.10.bb => sudo_1.9.12p1.bb} | 2 +-
...djust-range-v5.10.137-in-block-probe.patch | 92 --------------
...4-fix-kernel-crash-caused-by-do_get_.patch | 94 --------------
...ules_2.13.5.bb => lttng-modules_2.13.7.bb} | 4 +-
.../lttng/lttng-tools/determinism.patch | 2 +-
...-tools_2.13.4.bb => lttng-tools_2.13.8.bb} | 11 +-
...m-sysv-reverted-clang-VFP-mitigation.patch | 2 +-
scripts/lib/wic/partition.py | 29 ++++-
51 files changed, 474 insertions(+), 303 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/minidebuginfo.py
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/0001-avoid-start-failure-with-bind-user.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/0001-named-lwresd-V-and-start-log-hide-build-options.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/bind-ensure-searching-for-json-headers-searches-sysr.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/bind9 (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/conf.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/generate-rndc-key.sh (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/init.d-add-support-for-read-only-rootfs.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/make-etc-initd-bind-stop-work.patch (100%)
rename meta/recipes-connectivity/bind/{bind-9.18.7 => bind-9.18.8}/named.service (100%)
rename meta/recipes-connectivity/bind/{bind_9.18.7.bb => bind_9.18.8.bb} (97%)
delete mode 100644 meta/recipes-connectivity/socat/socat/0001-configure.ac-check-getprotobynumber_r-with-AC_TRY_LI.patch
rename meta/recipes-connectivity/socat/{socat_1.7.4.3.bb => socat_1.7.4.4.bb} (89%)
create mode 100644 meta/recipes-core/dbus/dbus/0001-dbus-marshal-byteswap-Byte-swap-Unix-fd-indexes-if-n.patch
create mode 100644 meta/recipes-core/dbus/dbus/0001-dbus-marshal-validate-Check-brackets-in-signature-ne.patch
create mode 100644 meta/recipes-core/dbus/dbus/0001-dbus-marshal-validate-Validate-length-of-arrays-of-f.patch
delete mode 100644 meta/recipes-core/expat/expat/CVE-2022-43680.patch
rename meta/recipes-core/expat/{expat_2.4.9.bb => expat_2.5.0.bb} (88%)
rename meta/recipes-core/libxcrypt/{libxcrypt-compat_4.4.28.bb => libxcrypt-compat_4.4.30.bb} (100%)
rename meta/recipes-core/libxcrypt/{libxcrypt_4.4.28.bb => libxcrypt_4.4.30.bb} (100%)
create mode 100644 meta/recipes-core/systemd/systemd/CVE-2022-3821.patch
rename meta/recipes-extended/sudo/{sudo_1.9.10.bb => sudo_1.9.12p1.bb} (96%)
delete mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-fix-adjust-range-v5.10.137-in-block-probe.patch
delete mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-wrapper-powerpc64-fix-kernel-crash-caused-by-do_get_.patch
rename meta/recipes-kernel/lttng/{lttng-modules_2.13.5.bb => lttng-modules_2.13.7.bb} (86%)
rename meta/recipes-kernel/lttng/{lttng-tools_2.13.4.bb => lttng-tools_2.13.8.bb} (90%)
--
2.25.1
next reply other threads:[~2022-11-23 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 14:18 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-11 2:36 [OE-core][kirkstone 00/35] Pull request (cover letter only) 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.1669212990.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 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.