public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/5] Patch review
Date: Fri,  3 Sep 2021 04:10:48 -1000	[thread overview]
Message-ID: <cover.1630678081.git.steve@sakoman.com> (raw)

Please review this next set of patches for dunfell and have comments back by
end of day Monday.

Passed a-full on autobuilder:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2540

The following changes since commit 448e0271ed831582bb5833486fc17b131676fb53:

  selftest: disable virgl headless test (2021-08-27 04:58:08 -1000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut

Andrej Valek (1):
  vim: add option to disable NLS support

Armin Kuster (1):
  lz4: Security Fix for CVE-2021-3520

Matt Madison (1):
  layer.conf: fix syntax error in PATH setting

Richard Purdie (1):
  sdk: Decouple default install path from built in path

Ross Burton (1):
  cpio: backport fix for CVE-2021-38185

 meta/classes/populate_sdk_base.bbclass        |   1 +
 meta/conf/bitbake.conf                        |   4 +-
 meta/conf/layer.conf                          |   2 +-
 meta/files/toolchain-shar-extract.sh          |   3 +-
 meta/files/toolchain-shar-relocate.sh         |   2 +-
 .../cpio/cpio-2.13/CVE-2021-38185.patch       | 581 ++++++++++++++++++
 meta/recipes-extended/cpio/cpio_2.13.bb       |   1 +
 .../lz4/files/CVE-2021-3520.patch             |  27 +
 meta/recipes-support/lz4/lz4_1.9.2.bb         |   1 +
 meta/recipes-support/vim/vim.inc              |   4 +-
 10 files changed, 621 insertions(+), 5 deletions(-)
 create mode 100644 meta/recipes-extended/cpio/cpio-2.13/CVE-2021-38185.patch
 create mode 100644 meta/recipes-support/lz4/files/CVE-2021-3520.patch

-- 
2.25.1


             reply	other threads:[~2021-09-03 14:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 14:10 Steve Sakoman [this message]
2021-09-03 14:10 ` [OE-core][dunfell 1/5] sdk: Decouple default install path from built in path Steve Sakoman
2021-09-03 14:10 ` [OE-core][dunfell 2/5] cpio: backport fix for CVE-2021-38185 Steve Sakoman
2021-09-03 14:10 ` [OE-core][dunfell 3/5] lz4: Security Fix for CVE-2021-3520 Steve Sakoman
2021-09-03 14:10 ` [OE-core][dunfell 4/5] vim: add option to disable NLS support Steve Sakoman
2021-09-03 14:10 ` [OE-core][dunfell 5/5] layer.conf: fix syntax error in PATH setting Steve Sakoman
  -- strict thread matches above, loose matches on Subject: below --
2024-04-10 13:10 [OE-core][dunfell 0/5] Patch review Steve Sakoman
2024-01-05 14:03 Steve Sakoman
2023-12-19 13:48 Steve Sakoman
2023-09-04 14:22 Steve Sakoman
2023-06-14 14:04 Steve Sakoman
2022-09-22 21:47 Steve Sakoman
2021-09-07 14:44 Steve Sakoman
2020-11-21  0:13 Steve Sakoman
2020-06-03 15:33 Steve Sakoman
2020-06-03 17:33 ` akuster
2020-06-03 17:36   ` Denys Dmytriyenko
2020-06-03 17:45     ` akuster
2020-06-03 23:33       ` Martin Jansa
2020-06-04  0:11         ` Joshua Watt
2020-06-04  0:38           ` Martin Jansa
2020-06-03 18:17     ` akuster
2020-06-03 18:18       ` Denys Dmytriyenko

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.1630678081.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