Bug 2177213
Summary: | Multiple grub2 binaries are not compiled with annobin plugin enabled | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Matus Marhefka <mmarhefk> |
Component: | grub2 | Assignee: | Bootloader engineering team <bootloader-eng-team> |
Status: | CLOSED MIGRATED | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.2 | CC: | jpazdziora, mlewando, raravind |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-16 19:07:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Matus Marhefka
2023-03-10 12:24:28 UTC
We already have a bug open for the same issue for grub2-tools-minimal: https://bugzilla.redhat.com/show_bug.cgi?id=2148125 which we have proposed to fix in 9.3. We can keep this one open for grub2-tools and probably fix both in the same release. The problem is, with the 2.06-27.el9_0.x86_64 version for which bug 2148125 was filed, annocheck reported Hardened: /usr/bin/grub2-mount: PASS: stack-prot test Here for 2.06-61.el9 we get skip: stack-prot test because sources compiled as if they were assembler are not checked by this test So it seems like some regression happened between RHEL 9.0 and the 9.2 build since for the RHEL 9.0 build the plugin was (likely) used because annocheck was happy with most of the binaries there. If there is a regression brewing for RHEL 9.2 compared to previous y-releases, maybe it should be prevented in RHEL 9.2. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |