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.
Bug 2121447 - broken symlink /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz
Summary: broken symlink /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: linux-firmware
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Patrick Talbert
QA Contact: Laura Trivelloni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-25 13:31 UTC by Pavel Cahyna
Modified: 2023-05-09 10:26 UTC (History)
2 users (show)

Fixed In Version: linux-firmware-20221012-128.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-09 08:18:55 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-132338 0 None None None 2022-08-25 13:46:38 UTC
Red Hat Product Errata RHBA-2023:2494 0 None None None 2023-05-09 08:19:09 UTC

Description Pavel Cahyna 2022-08-25 13:31:34 UTC 
Description of problem:

There is a broken symlink /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz in the linux-firmware package. The target brcmfmac43455-sdio.pine64,quartz64-b.txt.xz is not shipped in any released RPM:
# yum repoquery --whatprovides /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz
linux-firmware-0:20220708-127.el9.noarch
# yum repoquery --whatprovides /usr/lib/firmware/brcm/brcmfmac43455-sdio.pine64,quartz64-b.txt.xz
<nothing>

This is annoying, because there is a utility (ReaR) that produces a bootable rescue image (including modules and firmware) and checks whether the content of the image is valid. If it encounters a broken symlink, it complains, because it indicates a potential problem and it will be then seen as false alarm that can ultimately obscure a real problem (see bz2021935).

Since the target does not exist, I suppose the best solution would be to remove the symlink from the package (or include the target, if it has been omitted by mistake).

Version-Release number of selected component (if applicable):
0:20220708-127.el9
How reproducible:
easily in the default install

Steps to Reproduce:
1. file /usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz

Actual results:
/usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz: broken symbolic link to brcmfmac43455-sdio.pine64,quartz64-b.txt.xz

Expected results:
symlink is readable

Additional info:
"pine64" suggests that it is something ARM-specific, but even on aarch64 the symlink is broken and nothing provides the target (the package is noarch anyway).
Comment 1 Pavel Cahyna 2022-08-25 13:45:54 UTC 
Interestingly, the problem is not present in RHEL 9.0, package linux-firmware-20220209-126.el9_0.noarch does not contain this symlink at all.
Comment 2 Patrick Talbert 2022-08-30 11:05:12 UTC 
This is actually caused by an error in the linux-firmware WHENCE file.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f8a2651ac243e7167460f59be4f9db6b135d631b


The WHENCE file Link: syntax is 'Link: {TARGET} -> {SOURCE}' but in the above commit it is erroneously reversed. Let me figure out where to send the patch upstream...
Comment 3 Patrick Talbert 2022-08-30 12:25:59 UTC 
Ah, this is fixed already by dfa2931/35bb3bdd which are included in the 20220815 release.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=dfa29317dd78f3a18f37ef8063efe9d2659e6387
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=35bb3bdd5c14a411ec21b0da34bdbbe7441cc738
Comment 16 errata-xmlrpc 2023-05-09 08:18:55 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 (linux-firmware 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/RHBA-2023:2494
Note You need to log in before you can comment on or make changes to this bug.