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).
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.
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...
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
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