All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [gatesgarth][PATCH 0/8] review request
Date: Wed, 21 Apr 2021 14:06:12 +0800	[thread overview]
Message-ID: <cover.1618984878.git.anuj.mittal@intel.com> (raw)

Please review these next set of changes for gatesgarth. These build
cleanly on autobuilder except two intermittent and unrelated failures.

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

Thanks,

Anuj

The following changes since commit d1283b74cc29d1cbcab56bf1075a244ea5082025:

  image-live.bbclass: optional depends when ROOTFS empty (2021-04-09 14:04:40 +0800)

are available in the Git repository at:

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

Chen Qi (1):
  busybox: fix CVE-2021-28831

Douglas Royds (1):
  externalsrc: Detect code changes in submodules

Peter Budny (1):
  lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9)

Richard Purdie (3):
  pseudo: Upgrade to add trailing slashes ignore path fix
  oeqa/selftest: Hardcode test assumptions about heartbeat event timings
  sanity: Add error check for '%' in build path

Ross Burton (1):
  insane: clean up some more warning messages

Stefan Ghinea (1):
  wpa-supplicant: fix CVE-2021-30004

 meta/classes/externalsrc.bbclass              |  11 +-
 meta/classes/insane.bbclass                   |  12 +-
 meta/classes/sanity.bbclass                   |   2 +
 meta/lib/oe/terminal.py                       |  16 ++-
 meta/lib/oeqa/selftest/cases/buildoptions.py  |   6 +-
 .../wpa-supplicant/CVE-2021-30004.patch       | 123 ++++++++++++++++++
 .../wpa-supplicant/wpa-supplicant_2.9.bb      |   1 +
 ...ss_gunzip-Fix-DoS-if-gzip-is-corrupt.patch |  58 +++++++++
 meta/recipes-core/busybox/busybox_1.32.0.bb   |   3 +-
 meta/recipes-devtools/pseudo/pseudo_git.bb    |   2 +-
 10 files changed, 215 insertions(+), 19 deletions(-)
 create mode 100644 meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/CVE-2021-30004.patch
 create mode 100644 meta/recipes-core/busybox/busybox/0001-decompress_gunzip-Fix-DoS-if-gzip-is-corrupt.patch

-- 
2.30.2


             reply	other threads:[~2021-04-21  6:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  6:06 Anuj Mittal [this message]
2021-04-21  6:06 ` [gatesgarth][PATCH 1/8] pseudo: Upgrade to add trailing slashes ignore path fix Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 2/8] lib/oe/terminal: Fix tmux new-session on older tmux versions (<1.9) Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 3/8] oeqa/selftest: Hardcode test assumptions about heartbeat event timings Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 4/8] sanity: Add error check for '%' in build path Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 5/8] insane: clean up some more warning messages Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 6/8] externalsrc: Detect code changes in submodules Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 7/8] wpa-supplicant: fix CVE-2021-30004 Anuj Mittal
2021-04-21  6:06 ` [gatesgarth][PATCH 8/8] busybox: fix CVE-2021-28831 Anuj Mittal
  -- strict thread matches above, loose matches on Subject: below --
2021-04-26  5:45 [gatesgarth][PATCH 0/8] review 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.1618984878.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.