sreadahead crashed with SIGSEGV in __pause_nocancel()

Bug #446418 reported by Misha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sreadahead (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: sreadahead

Description: Ubuntu karmic (development branch)
Release: 9.10

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 8 19:08:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/sreadahead
NonfreeKernelModules: fglrx
Package: sreadahead 1.0-4
ProcCmdline: /sbin/sreadahead -t 0
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x401f3b: mov (%r15,%rdi,1),%dil
 PC (0x00401f3b) ok
 source "(%r15,%rdi,1)" (0x7f7b2887f010) not located in a known VMA region (needed readable region)!
 destination "%dil" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: sreadahead
StacktraceTop:
 __pause_nocancel () from /lib/libpthread.so.0
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: sreadahead crashed with SIGSEGV in __pause_nocancel()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:

Revision history for this message
Misha (mishailpetrov) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.