From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 0/6] Pull request
Date: Thu, 17 Mar 2022 22:14:22 +0800 [thread overview]
Message-ID: <cover.1647526261.git.anuj.mittal@intel.com> (raw)
The following changes since commit d0b1807edc10835beff9a55a105ac191b6ac2fe7:
unfs3: correct configure option (2022-03-07 22:19:01 +0800)
are available in the Git repository at:
git://push.openembedded.org/openembedded-core-contrib stable/hardknott-next
Bill Pittman (1):
wic: Use custom kernel path if provided
Jose Quaresma (1):
sstate: inside the threadedpool don't write to the shared localdata
Kai Kang (2):
expat: fix CVE-2022-25235
expat: fix CVE-2022-25236
Pavel Zhukov (1):
patch.py: Prevent git repo reinitialization
Richard Purdie (1):
vim: Update to 8.2.4524 for further CVE fixes
.../recipes-test/gitrepotest/gitrepotest.bb | 16 ++
.../gitrepotest/0001-testpatch.patch | 9 +
meta/classes/sstate.bbclass | 2 +-
meta/lib/oe/patch.py | 11 +-
meta/lib/oeqa/selftest/cases/bbtests.py | 18 +-
.../expat/expat/CVE-2022-25235.patch | 261 ++++++++++++++++++
.../expat/expat/CVE-2022-25236-1.patch | 116 ++++++++
.../expat/expat/CVE-2022-25236-2.patch | 232 ++++++++++++++++
meta/recipes-core/expat/expat_2.2.10.bb | 3 +
meta/recipes-support/vim/vim.inc | 4 +-
scripts/wic | 3 +
11 files changed, 667 insertions(+), 8 deletions(-)
create mode 100644 meta-selftest/recipes-test/gitrepotest/gitrepotest.bb
create mode 100644 meta-selftest/recipes-test/gitrepotest/gitrepotest/0001-testpatch.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-25235.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-25236-1.patch
create mode 100644 meta/recipes-core/expat/expat/CVE-2022-25236-2.patch
--
2.35.1
reply other threads:[~2022-03-17 14: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.1647526261.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox