Bug 580974 - rpm2cpio does not handle partial reads and writes properly
Summary: rpm2cpio does not handle partial reads and writes properly
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rpm
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-09 16:44 UTC by Tom Marshall
Modified: 2013-03-07 13:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-07 13:25:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Handle partial reads and writes in rpmio lib (1.24 KB, patch)
2010-04-09 16:44 UTC, Tom Marshall
no flags Details | Diff

Description Tom Marshall 2010-04-09 16:44:58 UTC
Created attachment 405581 [details]
Handle partial reads and writes in rpmio lib

Description of problem:

If rpm2cpio receives certain signals, such as SIGCONT, read and write may return EINTR, which results in partial libc reads and writes.  This is not handled properly and results in incorrect behavior.

Please find the attached patch to fix the issue.

Comment 1 Panu Matilainen 2013-03-07 13:25:30 UTC
This request was evaluated by Red Hat Engineering for inclusion in a Red Hat Enterprise Linux maintenance release.

Red Hat does not currently plan to provide this change in a Red Hat Enterprise Linux update release for currently deployed products.

With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating enhancements for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects. 

This should be fixed in Red Hat Enterprise Linux >= 6.4 however.


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