Bug 1402682

Summary: [abrt] virt-manager: setcontext(): python2.7 killed by SIGSEGV: TAINTED
Product: [Fedora] Fedora Reporter: Han Han <hhan>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: berrange, crobinso, pgervase, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a02f14e46078d00cbf88877a497c1cc1bb3e4586
Whiteboard: abrt_hash:fe66b12b6739d79e31c225f6084040db05f1091c;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-12 22:20:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Han Han 2016-12-08 06:59:20 UTC 
Description of problem:


Version-Release number of selected component:
virt-manager-1.4.0-4.fc26

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/python2 /usr/share/virt-manager/virt-manager
crash_function: setcontext
executable:     /usr/bin/python2.7
global_pid:     7969
kernel:         4.9.0-0.rc6.git2.1.fc26.x86_64
pkg_fingerprint: 812A 6B4B 64DA B85D
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 0 (2 frames)
 #0 setcontext at ../sysdeps/unix/sysv/linux/x86_64/setcontext.S:55
 #1 __start_context at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:39
Comment 1 Han Han 2016-12-08 06:59:30 UTC 
Created attachment 1229364 [details]
File: backtrace
Comment 2 Han Han 2016-12-08 06:59:32 UTC 
Created attachment 1229365 [details]
File: cgroup
Comment 3 Han Han 2016-12-08 06:59:34 UTC 
Created attachment 1229366 [details]
File: core_backtrace
Comment 4 Han Han 2016-12-08 06:59:37 UTC 
Created attachment 1229367 [details]
File: dso_list
Comment 5 Han Han 2016-12-08 06:59:39 UTC 
Created attachment 1229368 [details]
File: environ
Comment 6 Han Han 2016-12-08 06:59:40 UTC 
Created attachment 1229369 [details]
File: limits
Comment 7 Han Han 2016-12-08 06:59:44 UTC 
Created attachment 1229370 [details]
File: maps
Comment 8 Han Han 2016-12-08 06:59:45 UTC 
Created attachment 1229371 [details]
File: mountinfo
Comment 9 Han Han 2016-12-08 06:59:47 UTC 
Created attachment 1229372 [details]
File: namespaces
Comment 10 Han Han 2016-12-08 06:59:49 UTC 
Created attachment 1229373 [details]
File: open_fds
Comment 11 Han Han 2016-12-08 06:59:51 UTC 
Created attachment 1229374 [details]
File: proc_pid_status
Comment 12 Han Han 2016-12-08 06:59:52 UTC 
Created attachment 1229375 [details]
File: var_log_messages
Comment 13 Cole Robinson 2016-12-12 22:20:33 UTC 
This backtrace doesn't make much sense, and given that the report is marked TAINTED I'm guessing this is some kernel weirdness that we can't fix on an app side