Bug 158743 - tar-1.14-err.patch causes SEGV
tar-1.14-err.patch causes SEGV
Product: Fedora
Classification: Fedora
Component: tar (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Vrabec
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2005-05-25 08:28 EDT by Mark Williams
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-26 09:18:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark Williams 2005-05-25 08:28:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705)

Description of problem:
Attempting to create a listed-incremental archive of a directory hierarchy containing a directory without read permission (and at least one other sibling file/ directory) causes a SEGV due to uninitialised memory while sorting.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
As a non-superuser:

% umask 077
% mkdir mydir
% mkdir mydir/noreaddir
% chmod u-r mydir/noreaddir
% touch mydir/file
% tar -cf mydir.tar -g mydir.listed mydir

Additional info:

This is caused by tar-1.14-err.patch---which AFAICT serves no useful purpose anyway (nor would it under later versions up to and including the current 1.15.1) because the function in question (scan_path) already handles the case of dirp being NULL (and then correctly terminates the obstack frame).

I suggest this patch be entirely removed.
Comment 1 Peter Vrabec 2005-07-21 11:54:43 EDT
I can not reproduce it. But when I look into code it seems to me you are right.
Comment 2 Peter Vrabec 2005-07-22 05:59:25 EDT
I got it. x86_64

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