RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1284906 - cp will corrupt sparse files with trailing extents
Summary: cp will corrupt sparse files with trailing extents
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: coreutils
Version: 7.2
Hardware: All
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Jakub Prokes
Petr Bokoc
URL:
Whiteboard:
Depends On:
Blocks: 1285365
TreeView+ depends on / blocked
 
Reported: 2015-11-24 12:48 UTC by Pádraig Brady
Modified: 2016-11-04 07:40 UTC (History)
5 users (show)

Fixed In Version: coreutils-8.22-16.el7
Doc Type: Bug Fix
Doc Text:
Copying sparse files with trailing extents using "cp" no longer causes data corruption When creating sparse files, the *fallocate* utility could allocate extents beyond EOF using `FALLOC_FL_KEEP_SIZE`. As a consequence, when there was a gap (hole) between the extents, and EOF was within that gap, the final hole was not reproduced, which caused silent data corruption in the copied file due to its size being too small. With this update, the "cp" command ensures that extents beyond the apparent file size are not processed, as such processing and allocating is not currently supported. As a result, silent data corruption in certain type of sparse files no longer occurs.
Clone Of:
: 1285365 (view as bug list)
Environment:
Last Closed: 2016-11-04 07:40:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2497 0 normal SHIPPED_LIVE coreutils bug fix update 2016-11-03 14:11:50 UTC

Description Pádraig Brady 2015-11-24 12:48:38 UTC 
cp will corrupt copies of a file that has:

1. a hole up to the apparent size of the file.
2. an extent after the apparent EOF.

To reproduce:

echo blabla > sparse_falloc.in
truncate -s 2M sparse_falloc.in
fallocate -n -o 4M -l 1M sparse_falloc.in
cp sparse_falloc.in sparse_falloc.out
cmp sparse_falloc.in sparse_falloc.out || echo corrupt

Upstream backportable fix is at:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=patch;h=eea6b49
Comment 1 Ondrej Vasik 2015-11-25 10:34:33 UTC 
Thanks Pádraig for heads-up.
Comment 10 errata-xmlrpc 2016-11-04 07:40:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2497.html
Note You need to log in before you can comment on or make changes to this bug.