Bug 882321
Summary: | file reports "unknown capability 0x41000000 = 0xf676e75" on PPC32 binaries | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Petr Machata <pmachata> |
Component: | file | Assignee: | Jan Kaluža <jkaluza> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | jkaluza, mnewsome |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-22 10:11:27 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
Petr Machata
2012-11-30 16:54:04 UTC
And the -fPIC is unnecessary. Please could you attach that binary if you still have access to some PowerPC machine? This is one such file: https://brewweb.devel.redhat.com/fileinfo?rpmID=2408671&filename=/usr/lib/debug/usr/bin/flex.debug The RPM can be download from here: https://brewweb.devel.redhat.com/buildinfo?buildID=229838 Apologies, I didn't realize the RPM link on that page that I linked wouldn't allow downloading. Thanks... It looks like it needs lot of changes in File's readelf.c code to support attributes properly. Turning this off for architectures where File currently does not support attributes would be easy, but implementing it for all archs is basically rewrite of big part of readelf.c. I will ask upstream what he thinks about it. Personally I think File should use some library to read elf files, but upstream is against external dependencies... The library wouldn't tell you anything more than what is available now anyway. The problem is in comparing section types that lie in OS-specific range. In binaries whose EI_OSABI has the value ELFOSABI_GNU, that particular value (0x6ffffff5) shouldn't be considered as SHT_SUNW_cap, but as SHT_GNU_ATTRIBUTES. It look like the information about EI_OSABI needs to be propagated from the part that parses Elf header to the part that takes care of parsing capabilities. Right, but then you have to start checking what's the data encoding (ELFDATA2MSB vs. ELFDATA2LSB) which is not handled in File right now and also rewrite whole attributes parsing logic to handle PPC and s390 attributes (which have different semantics). I'm not saying it's not possible, but I think it basically means rewrite of readelf.c. I will ask upstream what he thinks about it and if it wouldn't be better to use external library to do this instead of reinventing ELF parsing again. As a workaround I can patch File to not display attributes for PPC and S390 ELF binaries. It would not be a regression, because current state is broken anyway. Upstream thinks the proper way to fix it is to disable capabilities on currently unsupported e_machines. I've sent the patch upstream and will fix this bug once he accepts it. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |