Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 551028

Summary: app-benchmarks/i7z-0.27.2: crash on hardened (segmentation fault)
Product: Gentoo Linux Reporter: Sam James <sam>
Component: HardenedAssignee: The Gentoo Linux Hardened Team <hardened>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Ran with: "strace /usr/sbin/i7z"

Description Sam James archtester Gentoo Infrastructure gentoo-dev Security 2015-06-02 18:35:57 UTC
Program (/usr/bin/i7z or /usr/bin/i7z_gui) output:
i7z DEBUG: i7z version: svn-r77-(20-Nov-2011)
i7z DEBUG: Found Intel Processor
i7z DEBUG:    Stepping 7
i7z DEBUG:    Model a
i7z DEBUG:    Family 6
i7z DEBUG:    Processor Type 0
i7z DEBUG:    Extended Model 2
i7z DEBUG: msr = Model Specific Register
Segmentation fault

dmesg output:
[22092.063903] i7z[10510]: segfault at cb859225 ip 00000008cb64fb38 sp 000003a912d12ac0 error 6 in i7z[8cb64c000+d000]
[22092.063940] grsec: Segmentation fault occurred at 00000000cb859225 in /usr/sbin/i7z[i7z:10510] uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:9457] uid/euid:1000/1000 gid/egid:1000/1000
[22092.063956] grsec: more alerts, logging disabled for 10 seconds

Reproducible: Always

Steps to Reproduce:
1. Run Hardened kernel with PaX
2. emerge i7z
3. run with /usr/bin/i7z (or /usr/bin/i7z_GUI)
4. same output for both
Actual Results:  
Segmentation fault.
Comment 1 Jason Zaman gentoo-dev 2015-06-02 19:44:58 UTC
can you attach the output of running it with strace? and what is the exact command line you're using to run it?
Comment 2 Michael Palimaka (kensington) gentoo-dev 2015-06-02 19:51:36 UTC
dup of bug #487784 ?
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2015-06-02 21:25:42 UTC
Created attachment 404484 [details]
Ran with: "strace /usr/sbin/i7z"
Comment 4 Magnus Granberg gentoo-dev 2015-07-04 14:30:59 UTC

*** This bug has been marked as a duplicate of bug 487784 ***