Bug 7538 – cpio (cpio-2.4.2-13) closes filedescriptor to early

Bug 7538 - cpio (cpio-2.4.2-13) closes filedescriptor to early

Summary:	cpio (cpio-2.4.2-13) closes filedescriptor to early

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	cpio (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	high Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	bero
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-12-03 09:18 EST by Karsten Hopp
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-12-17 13:52:30 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Karsten Hopp 1999-12-03 09:18:48 EST

There's a new bug in release 13 of cpio. If you write an archive with
verbose-mode, the filedescriptor 1 will be closed and after that the
filename should be written to this descriptor.
Try this:
echo /etc/passwd | strace cpio -ocvB >/dev/null

The last few lines will look like this:

==>	close(1)                                = 0
==>	write(1, "/etc/passwd\n", 12)           = -1 EBADF (Bad file
descriptor)



        Karsten

Comment 1 Karsten Hopp 1999-12-04 08:36:59 EST

Should be an easy fix.
Shanged priority to 4high4, because several backup-systems rely on
the output of the filename after writing the archive.
(Return value is not valid on every system)

    Karsten

Comment 2 Jeff Johnson 1999-12-17 13:52:59 EST

I believe that this problem is fixed by reverting the stdout patch (#3358)
that has been done in cpio-2.4.2-14. Please reopen this bug if I'm wrong.

Comment 3 Karsten Hopp 1999-12-20 05:39:59 EST

Ok, it's fixed.

 Thanks
         Karsten

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