Bug 677935 - missing ')' in the output of "file /boot/vmlinuz*"
Summary: missing ')' in the output of "file /boot/vmlinuz*"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: file
Version: 6.1
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Jan Kaluža
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 10:14 UTC by Milos Malik
Modified: 2011-02-22 14:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-22 14:07:55 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Milos Malik 2011-02-16 10:14:18 UTC 
Description of problem:


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

How reproducible:
always

Steps to Reproduce:
(i686 machine)
# file /boot/vmlinuz-2.6.32-114.0.1.el6.i686
/boot/vmlinuz-2.6.32-114.0.1.el6.i686: Linux kernel x86 boot executable bzImage, version 2.6.32-114.0.1.el6.i686 (mockbu, RO-rootFS, root_dev 0x901, swap_dev 0x3, Normal VGA

(x86_64 machine)
# file /boot/vmlinuz-2.6.32-114.0.1.el6.x86_64 
/boot/vmlinuz-2.6.32-114.0.1.el6.x86_64: Linux kernel x86 boot executable bzImage, version 2.6.32-114.0.1.el6.x86_64 (mock, RO-rootFS, root_dev 0x901, swap_dev 0x3, Normal VGA


Actual results:
')' is missing

Expected results:
')' is present
Comment 2 Jan Kaluža 2011-02-22 14:07:55 UTC 
Missing '(' is not "typical" File bug. "(" is part of this kernel version string. File loads max 32-byte string from files, so the version string is not complete and therefore the ')' is missing.

32 bytes limit can be increased by patch from Bug 462378, but we can increase it only to 64, because that's what upstream did. From my tests 64 bytes are not enough to display linux version string, so I think I'll use NOT A BUG here.
Comment 3 Jan Kaluža 2011-02-22 14:16:57 UTC 
Hm, Don't understand how it happend, but correct bug is Bug 656395
Note You need to log in before you can comment on or make changes to this bug.