Bug 876840

Summary: [abrt] rtorrent-0.9.3-3.fc17: handle_sigbus: Process /usr/bin/rtorrent was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: frywalker <fry.futurateam>
Component: rtorrentAssignee: Conrad Meyer <cse.cem+redhatbugz>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: cse.cem+redhatbugz, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9a2417395167ad4281ce2db60145d207b029829b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 02:34:32 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: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description frywalker 2012-11-15 06:14:57 UTC
Description of problem:
The hard drive has been removed before unmounting.

Version-Release number of selected component:
rtorrent-0.9.3-3.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        rtorrent how.i.met.your.mother.7x20.hdtv.lol.torrent How.I.Met.Your.Mother.7x21.torrent 'How I Met Your Mother 8x02 (HDTV-x264-LOL) [VTV] [h33t].torrent' 'How I Met Your Mother 8x04 HDTV x264-LOL [VTV] [h33t].torrent' how.i.met.your.mother.s07e22.hdtv.x264.lol.vtv.mp4.torrent how.i.met.your.mother.s08e01.hdtv.x264.lol.vtv.mp4.torrent How_I_Met_Your_Mother_S08E03_HDTV_x264-LOL_[VTV]_mp4.torrent how.i.met.your.mother.s08e05.hdtv.x264.lol.vtv.mp4.torrent how.i.met.your.mother.s08e06.hdtv.x264.lol.vtv.mp4.torrent
crash_function: handle_sigbus
kernel:         3.6.6-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (9 frames)
: #2 handle_sigbus at main.cc:949
: #4 memcpy at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:119
: #6 torrent::Chunk::to_buffer at chunk.cc:217
: #7 up_chunk_encrypt at peer_connection_base.cc:709
: #8 torrent::PeerConnectionBase::up_chunk at peer_connection_base.cc:738
: #9 torrent::PeerConnection<(torrent::Download::ConnectionType)1>::event_write at peer_connection_leech.cc:617
: #10 torrent::PollEPoll::perform at poll_epoll.cc:183
: #11 torrent::PollEPoll::do_poll at poll_epoll.cc:210
: #12 torrent::thread_base::event_loop at thread_base.cc:145

Comment 1 frywalker 2012-11-15 06:15:00 UTC
Created attachment 645357 [details]
File: core_backtrace

Comment 2 frywalker 2012-11-15 06:15:02 UTC
Created attachment 645358 [details]
File: environ

Comment 3 frywalker 2012-11-15 06:15:05 UTC
Created attachment 645359 [details]
File: event_log

Comment 4 frywalker 2012-11-15 06:15:07 UTC
Created attachment 645360 [details]
File: limits

Comment 5 frywalker 2012-11-15 06:15:10 UTC
Created attachment 645361 [details]
File: backtrace

Comment 6 frywalker 2012-11-15 06:15:13 UTC
Created attachment 645362 [details]
File: cgroup

Comment 7 frywalker 2012-11-15 06:15:14 UTC
Created attachment 645363 [details]
File: smolt_data

Comment 8 frywalker 2012-11-15 06:15:17 UTC
Created attachment 645364 [details]
File: executable

Comment 9 frywalker 2012-11-15 06:15:19 UTC
Created attachment 645365 [details]
File: maps

Comment 10 frywalker 2012-11-15 06:15:21 UTC
Created attachment 645366 [details]
File: dso_list

Comment 11 frywalker 2012-11-15 06:15:23 UTC
Created attachment 645367 [details]
File: proc_pid_status

Comment 12 frywalker 2012-11-15 06:15:25 UTC
Created attachment 645368 [details]
File: var_log_messages

Comment 13 frywalker 2012-11-15 06:15:27 UTC
Created attachment 645369 [details]
File: open_fds

Comment 14 Conrad Meyer 2012-11-15 06:51:42 UTC
Based on the user comment, "The hard drive has been removed," I'm guessing this
is a side effect of memcpy()ing into a now bogus region of a file. From the mmap man page:

       Use of a mapped region can result in these signals:
...
       SIGBUS Attempted access to a portion of the buffer that does not corre‐
              spond to the file (for example, beyond  the  end  of  the  file,
              including  the  case  where  another  process  has truncated the
              file).

So, what should rtorrent do? It's going to have to do something messy to figure out which file went away, and likely others went away too.

Comment 15 Conrad Meyer 2012-11-15 06:56:23 UTC
Upstream issue: http://libtorrent.rakshasa.no/ticket/2670

Comment 16 Fedora End Of Life 2013-07-03 23:40:03 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 17 Fedora End Of Life 2013-08-01 02:34:36 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.