public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [hardknott][PATCH 0/7] Review request
Date: Sun, 15 Aug 2021 23:56:39 +0800	[thread overview]
Message-ID: <cover.1629041998.git.anuj.mittal@intel.com> (raw)

Please review this next set of patches for hardknott. Two intermittent
and unrelated failures seen while testing - a valgrind ptest failure and
a bitbake timeout while running a oe-selftest.

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

Thanks,

Anuj

The following changes since commit 49868162a1a1d088fbaabeffcc2debcbfc17b026:

  nettle: update 3.7.2 -> 3.7.3 (2021-08-09 10:19:38 +0800)

are available in the Git repository at:

  git://push.openembedded.org/openembedded-core-contrib anujm/hardknott

Armin Kuster (1):
  gnutls: Enable seccomp if FEATURE is set

Khem Raj (1):
  gnutls: Point to staging area for finding seccomp libs and includes

Sakib Sajal (3):
  qemu: fix CVE-2021-3582
  qemu: fix CVE-2021-3607
  qemu: fix CVE-2021-3608

Vinay Kumar (1):
  glibc: Fix CVE-2021-35942

wangmy (1):
  gnutls: upgrade 3.7.1 -> 3.7.2

 .../glibc/glibc/CVE-2021-35942.patch          | 44 +++++++++++++++++
 meta/recipes-core/glibc/glibc_2.33.bb         |  1 +
 meta/recipes-devtools/qemu/qemu.inc           |  3 ++
 .../qemu/qemu/CVE-2021-3582.patch             | 47 +++++++++++++++++++
 .../qemu/qemu/CVE-2021-3607.patch             | 43 +++++++++++++++++
 .../qemu/qemu/CVE-2021-3608.patch             | 43 +++++++++++++++++
 .../{gnutls_3.7.1.bb => gnutls_3.7.2.bb}      |  6 +--
 7 files changed, 184 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-core/glibc/glibc/CVE-2021-35942.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3582.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3607.patch
 create mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2021-3608.patch
 rename meta/recipes-support/gnutls/{gnutls_3.7.1.bb => gnutls_3.7.2.bb} (89%)

-- 
2.31.1


             reply	other threads:[~2021-08-15 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15 15:56 Anuj Mittal [this message]
2021-08-15 15:56 ` [hardknott][PATCH 1/7] glibc: Fix CVE-2021-35942 Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 2/7] qemu: fix CVE-2021-3582 Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 3/7] qemu: fix CVE-2021-3607 Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 4/7] qemu: fix CVE-2021-3608 Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 5/7] gnutls: Enable seccomp if FEATURE is set Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 6/7] gnutls: Point to staging area for finding seccomp libs and includes Anuj Mittal
2021-08-15 15:56 ` [hardknott][PATCH 7/7] gnutls: upgrade 3.7.1 -> 3.7.2 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.1629041998.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