Bug 450109 - cpio stores incorrect device nodes if major > 128
Summary: cpio stores incorrect device nodes if major > 128
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cpio
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-05 13:08 UTC by Jon Burgess
Modified: 2008-07-18 23:07 UTC (History)
2 users (show)

Fixed In Version: 2.9-8.fc9
Clone Of:
Environment:
Last Closed: 2008-07-18 23:07:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Burgess 2008-06-05 13:08:17 UTC
Description of problem:
While packing and unpacking some CPIO archives I saw the following error
cpio: dev/uba: Invalid argument


Version-Release number of selected component (if applicable):
cpio-2.9-7.fc9.x86_64

How reproducible:
every time

Steps to Reproduce:
find /dev/ | cpio -o | cpio -vt | grep 42949
  
Actual results:
Lots of device nodes get reported like...
crw-------   1 jburgess tty      4294967176, 4294967046 Jun  4 21:57 /dev/pts/6

Expected results:
$ ls -l /dev/pts/6
crw------- 1 jburgess tty 136, 6 2008-06-04 21:57 /dev/pts/6


Additional info:
Seems to happen for any device node with major number > 128
Machine above runs kernel-2.6.25.3-18.fc9.x86_64
The same is seen on machines running RedHat Enterprise Linux 4.6 and 5.1 as well.

Comment 1 Jon Burgess 2008-06-05 13:37:55 UTC
This problem does not effect the "-c" format. It isn't clear whether the default
format should support these higher major numbers. A warning would be nice.


Comment 2 Fedora Update System 2008-07-18 11:15:58 UTC
cpio-2.9-8.fc9 has been submitted as an update for Fedora 9

Comment 3 Fedora Update System 2008-07-18 23:07:31 UTC
cpio-2.9-8.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


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