Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
In RHEL-8.2, edk2 is based on edk2-stable201908 (according to bug
1748180).
There are (and/or soon will be) a number of upstream features / bugfixes
that we should inherit by rebasing to the (upcoming) edk2-stable202005
release.
* Upstream releases we'd incorporate:
- https://github.com/tianocore/edk2/releases/tag/edk2-stable201911
- https://github.com/tianocore/edk2/releases/tag/edk2-stable202002
- https://github.com/tianocore/edk2/releases/tag/edk2-stable202005
(note: this link will start working later; at the time of writing,
refer to
<https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#edk2-stable202005-tag-planning>)
* Upstream changes we want:
- BZ#1808845
(Upstream commit range 3b9cd714542a..7288ff4095cf.)
- BZ#1801276
(Depends on the TianoCore#2550 upstream tracker bug, which in turn
depends on TianoCore#1610, TianoCore#2031, TianoCore#2032,
TianoCore#2174. From those, the first two have been fixed (upstream
commit 578bcdc2605e, upstream commit 1d3215fd24f4), and the last two
have patches pending review on the list.)
- BZ#1747935
(Upstream commit range 578bcdc2605e..c230c002accc.)
- BZ#1454803
(Upstream commit range 61d3b2d4279e..1158fc8e2c7b.)
- BZ#1758153
(Upstream commit range ecb30848fdc9..61d3b2d4279e.)
* Upstream additions we should disable (via build flag updates in the
spec file), until/unless we get specific customer requests for
enabling them:
- Fusion-MPT SCSI driver (TianoCore#2390)
- VMware PVSCSI driver (TianoCore#2567)
- (TPM2 in ArmVirtQemu (TianoCore#2560) -- disabled by default anyway)
* Virt-QE should please pay special attention to regression-testing
cases that load the kernel & initrd via fw_cfg, in both edk2-ovmf and
edk2-aarch64. For example, network URL installs done with
"virt-install --location" do that ("virt-install will download
kernel/initrd to the local machine [...]").
This request is due to TianoCore#2566 ("use loadimage/startimage for
loading the kernel passed via the QEMU command line").
Since the last (= BZ#1748180), upstream edk2 has introduced four new
submodules:
- TianoCore#2505 [0eb522987fcd8] ->
UnitTestFrameworkPkg/Library/CmockaLib/cmocka
- TianoCore#2073 [48b6c60cc6a23] ->
MdeModulePkg/Universal/RegularExpressionDxe/oniguruma
- TianoCore#2558 [06033f5abad38] ->
BaseTools/Source/C/BrotliCompress/brotli
- TianoCore#2559 [58802e02c41bd] ->
MdeModulePkg/Library/BrotliCustomDecompressLib/brotli
None of these are necessary for building edk2-ovmf and edk2-aarch64.
Brotli *seems* necessary, but that's an accidental dependency, not an
inherent one.
While RHEL8 provides a brotli package, bundling the source code of that
with edk2 -- similarly to how we handle OpenSSL -- is not welcome: it's
useless complexity. Instead:
(1) The BaseTools dependency on the submodule (from TianoCore#2558) can
be eliminated like this:
> diff --git a/BaseTools/Source/C/GNUmakefile b/BaseTools/Source/C/GNUmakefile
> index df4eb64ea95e..52777eaff160 100644
> --- a/BaseTools/Source/C/GNUmakefile
> +++ b/BaseTools/Source/C/GNUmakefile
> @@ -45,7 +45,6 @@ all: makerootdir subdirs
> LIBRARIES = Common
> VFRAUTOGEN = VfrCompile/VfrLexer.h
> APPLICATIONS = \
> - BrotliCompress \
> VfrCompile \
> EfiRom \
> GenFfs \
(Note that, accordingly, the "Brotli" utility can be dropped from the
edk2-tools package, as edk2-tools is not shipped in AppStream.)
(2) The MdeModulePkg dependency on the submodule (from TianoCore#2559)
can be eliminated like this (as neither the ArmVirtQemu platform nor the
OVMF platform consumes BrotliCustomDecompressLib):
> diff --git a/MdeModulePkg/MdeModulePkg.dec b/MdeModulePkg/MdeModulePkg.dec
> index 42ad21cf244d..568d024e5e52 100644
> --- a/MdeModulePkg/MdeModulePkg.dec
> +++ b/MdeModulePkg/MdeModulePkg.dec
> @@ -25,7 +25,6 @@ [Includes]
> Include
>
> [Includes.Common.Private]
> - Library/BrotliCustomDecompressLib/brotli/c/include
>
> [LibraryClasses]
> ## @libraryclass Defines a set of methods to reset whole system.
(Tested the above as of upstream commit 06033f5abad3 ("BaseTools: Make
brotli a submodule", 2020-04-16).)
(In reply to Laszlo Ersek from comment #0)
> * Upstream additions we should disable (via build flag updates in the
> spec file), until/unless we get specific customer requests for
> enabling them:
>
> [...]
>
> - (TPM2 in ArmVirtQemu (TianoCore#2560) -- disabled by default anyway)
See bug 1837452 though.
Comment 14leidwang@redhat.com
2020-06-28 01:16:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: edk2 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:4805