Bug 2106651

Summary: tar: error extracting sparse file >= 8G archived by bsdtar
Product: Red Hat Enterprise Linux 9 Reporter: Lukas Javorsky <ljavorsk>
Component: libarchiveAssignee: Lukas Javorsky <ljavorsk>
Status: CLOSED ERRATA QA Contact: Vaclav Danek <vdanek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: databases-maint, jkejda, ljavorsk, pkubat, vdanek, zmiklank
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libarchive-3.5.3-3.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 11:22:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Javorsky 2022-07-13 08:28:42 UTC
This bug was initially created as a copy of Bug #2037839

I am copying this bug because: 

The same version of libarchive is present in RHEL-9. To avoid regression, we need to fix this here as well.


Tar fails with error (EOF) when trying to extract archive created by bsdtar containing sparse file with size >= 8G.

Error:
tar -xzf archive.tar.gz -C extract
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.selinux'
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

Reproducer:
reproducer attached

Package versions:
tar-1.30-5.el8.x86_64
bsdtar-3.3.3-1.el8.x86_64

Comment 3 Lukas Javorsky 2022-07-18 09:05:08 UTC
Merged

Comment 11 errata-xmlrpc 2022-11-15 11:22:04 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 (libarchive bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:8377