Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 720324

Summary:	File does not correctly identify a linux kernel image on ppc64
Product:	Red Hat Enterprise Linux 6	Reporter:	Karel Srot <ksrot>
Component:	file	Assignee:	Jan Kaluža <jkaluza>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-08-23 08:51:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Srot 2011-07-11 11:52:49 UTC

Description of problem:

# file /boot/vmlinuz-2.6.32-*
/boot/vmlinuz-2.6.32-131.2.1.el6.ppc64:       ELF 64-bit MSB shared object,
64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped
/boot/vmlinuz-2.6.32-131.2.1.el6.ppc64.debug: ELF 64-bit MSB shared object,
64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped
/boot/vmlinuz-2.6.32-131.4.1.el6.ppc64:       ELF 64-bit MSB shared object,
64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped
/boot/vmlinuz-2.6.32-131.4.1.el6.ppc64.debug: ELF 64-bit MSB shared object,
64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped
/boot/vmlinuz-2.6.32-71.el6.ppc64:            ELF 64-bit MSB shared object,
64-bit PowerPC or cisco 7500, version 1 (SYSV), statically linked, stripped

Version-Release number of selected component (if applicable):
file-5.04-9.el6

How reproducible:
always

Expected results:
something similar to x86_64 output
on x86_64:

file /boot/vmlinuz-2.6.32-71.el6.x86_64 
/boot/vmlinuz-2.6.32-71.el6.x86_64: Linux kernel x86 boot executable bzImage,
version 2.6.32-71.el6.x86_64 (mockbuild, RO-rootFS, root_dev 0x901, swap_dev
0x3, Normal VGA

Comment 2 Jan Kaluža 2011-08-23 08:51:49 UTC

I was trying to find something useful in ppc kernels to identify it as kernel instead of PowerPC binary, but I haven't found anything which could be used. There's no header like in i386 kernels and also no special bytes anywhere to identify it.

I will close it as WONTFIX.