Bug 866071

Summary: [abrt] tar-1.26-7.fc17: strncmp: Process /usr/bin/tar was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ahel ibn Alquivr <ahelibnalquivr>
Component: tarAssignee: Pavel Raiskup <praiskup>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: kdudka, ovasik, praiskup
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e6aa29657cb59249763149a45f6bed87558ce66c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-01 06:06:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: event_log
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description Ahel ibn Alquivr 2012-10-13 17:51:04 UTC 
Description of problem:
i was trying to untar a folder of 20Gb. Since I've commanded a -M it said "prepare the second volume and give enter", but since I didn't know what i was doing I entered enter and it crashed.

Version-Release number of selected component:
tar-1.26-7.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        tar -xf 'xxxxxxxxxx.tar' -M -ignore-failed-read
crash_function: strncmp
kernel:         3.5.4-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 strncmp at ../sysdeps/x86_64/strcmp.S
: #1 try_new_volume at buffer.c
: #2 _gnu_flush_read at buffer.c
: #3 gnu_flush_read at buffer.c
: #4 flush_read at buffer.c
: #5 flush_archive at buffer.c
: #6 find_next_block at buffer.c
: #7 extract_file at extract.c
: #8 extract_archive at extract.c
: #9 read_and at list.c
Comment 1 Ahel ibn Alquivr 2012-10-13 17:51:09 UTC 
Created attachment 626600 [details]
File: core_backtrace
Comment 2 Ahel ibn Alquivr 2012-10-13 17:51:14 UTC 
Created attachment 626601 [details]
File: environ
Comment 3 Ahel ibn Alquivr 2012-10-13 17:51:18 UTC 
Created attachment 626602 [details]
File: event_log
Comment 4 Ahel ibn Alquivr 2012-10-13 17:51:23 UTC 
Created attachment 626603 [details]
File: limits
Comment 5 Ahel ibn Alquivr 2012-10-13 17:51:32 UTC 
Created attachment 626604 [details]
File: backtrace
Comment 6 Ahel ibn Alquivr 2012-10-13 17:51:37 UTC 
Created attachment 626605 [details]
File: cgroup
Comment 7 Ahel ibn Alquivr 2012-10-13 17:51:42 UTC 
Created attachment 626606 [details]
File: maps
Comment 8 Ahel ibn Alquivr 2012-10-13 17:51:47 UTC 
Created attachment 626607 [details]
File: dso_list
Comment 9 Ahel ibn Alquivr 2012-10-13 17:51:55 UTC 
Created attachment 626608 [details]
File: var_log_messages
Comment 10 Ahel ibn Alquivr 2012-10-13 17:52:00 UTC 
Created attachment 626609 [details]
File: open_fds
Comment 11 Pavel Raiskup 2012-10-16 08:14:43 UTC 
Thanks for the report!

I'm able to reproduce your problem even with upstream tar.  I'll try to observe
where is the problem.

Pavel
Comment 12 Pavel Raiskup 2012-11-02 14:23:28 UTC 
Upstream proposal:

http://lists.gnu.org/archive/html/bug-tar/2012-11/msg00008.html
Comment 13 Fedora End Of Life 2013-07-04 06:27:38 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Pavel Raiskup 2013-07-04 07:09:18 UTC 
As this is upstream problem, moving to Rawhide (it can be backported to stable
release once fixed upstream).
Comment 15 Jan Kurik 2015-07-15 14:58:18 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Comment 16 Mike McCune 2016-03-28 23:21:47 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 17 Pavel Raiskup 2016-06-01 06:06:44 UTC 
The crash is fixed upstream: 0a93c16c6299d4ea91f2eb04f8c997d7d58f9af8

Released in v1.29 (F25+).