Red Hat Bugzilla – Bug 996150
Segmentation fault （core dumped） when cpio compress /sys directory
Last modified: 2014-10-22 03:15:07 EDT
Description of problem:
Segmentation fault （core dumped） when cpio compress /sys directory.
Version-Release number of selected component (if applicable):
[root@localhost tmp]# rpm -qi cpio
Name : cpio Relocations: (not relocatable)
Version : 2.10 Vendor: CentOS
Release : 9.el6 Build Date: Wed 10 Nov 2010 10:43:45 PM EST
Install Date: Sun 23 Jun 2013 03:23:13 AM EDT Build Host: c6b6.bsys.dev.centos.org
Group : Applications/Archiving Source RPM: cpio-2.10-9.el6.src.rpm
Size : 650610 License: GPLv3+
Signature : RSA/8, Sun 03 Jul 2011 12:08:07 AM EDT, Key ID 0946fca2c105b9de
Packager : CentOS BuildSystem <http://bugs.centos.org>
URL : http://www.gnu.org/software/cpio/
Summary : A GNU archiving program
Steps to Reproduce:
[root@localhost tmp]# find /sys |cpio -ocvB > a.cpio
cpio: /sys/devices/virtual/dmi/id/subsystem: Warning: Cannot readlink: Invalid argument
Segmentation fault (core dumped)
Thank you for taking the time to enter a bug report with us. We appreciate the
feedback and look to use reports such as this to guide our efforts at
improving our products. That being said, this bug tracking system is not a
mechanism for requesting support, and we are not able to guarantee the
timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket
through your regular Red Hat support channels to make certain it receives the
proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
Ups, bad bug. Sorry for previous comment.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 898389 [details]
Check that read() did not fail
Attaching another fix which checks return values for SAFE_READ_ERROR. This is
principally better approach.