Bug 2051618 - annocheck warnings during rpmdiff on MariaDB-10.5 files
Summary: annocheck warnings during rpmdiff on MariaDB-10.5 files
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mariadb
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Zuzana Miklankova
QA Contact: Jakub Heger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-07 15:53 UTC by Lukas Javorsky
Modified: 2023-08-07 07:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-07 07:28:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-111377 0 None None None 2022-02-07 16:13:37 UTC

Description Lukas Javorsky 2022-02-07 15:53:24 UTC
Description of problem:
annocheck ran on module-mariadb-10.5-8050020220204122540-c5368500 rpms shows warnings: 
"FAIL: optimization test because level too low (function: _Z19check_stack_overrunP3THDlPh)"

This exact warning is raised on these files:
./usr/bin/mariadb-test-embedded
./usr/bin/test-connect-t
./usr/libexec/mariadbd
./usr/lib64/libmariadbd.so.19
./usr/bin/mariadb-backup


Version-Release number of selected component (if applicable):
MariaDB-10.5.13-1

How reproducible:
Always

Steps to Reproduce:
1. Download all RPMs from module-mariadb-10.5-8050020220204122540-c5368500
2. annocheck *.rpm --verbose


Additional info:
This could be related to the BZ#2044388 even though it's not that critical (as agreed in the team) because these are different types of FAILS. But the solution could be the same.

We estimate to solve this on the next release of the MariaDB module.

Comment 4 RHEL Program Management 2023-08-07 07:28:19 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.