Bug 1394878 - binfmts are too strict
Summary: binfmts are too strict
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 15:57 UTC by Nathaniel McCallum
Modified: 2016-11-15 22:42 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 22:42:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nathaniel McCallum 2016-11-14 15:57:36 UTC
Specifically, e_ident[EI_OSABI]. The current binfmt config for most architectures requires e_ident[EI_OSABI] to be 0x00 (System V), but it is also common to have 0x03 (Linux) (and possibly others).

I ran into this problem executing a container with qemu-ppc64-static. In this case, the container (the official Fedora 24 ppc64 cloud image) contained binaries with multiple stated ABIs. The qemu-ppc64-static binary supports both ABIs (I tested).

I suspect the best solution is to simply mask out this byte since other ABIs might be supported as well. It appears all the mips related binfmts already do this. However, all the binfmts except for mips* have this problem.

Comment 1 Nathaniel McCallum 2016-11-15 22:42:26 UTC
Fixed in qemu-2.7.0-9.fc26.


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