Bug 369402 - Bad set/get_thread_area pointer crashes valgrind
Summary: Bad set/get_thread_area pointer crashes valgrind
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-26 21:09 UTC by Mark Wielaard
Modified: 2016-10-01 11:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
linux-x86 check get/set_thread_area pointer before use. (1.34 KB, patch)
2016-09-26 21:13 UTC, Mark Wielaard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2016-09-26 21:09:39 UTC
LTP testcases/kernel/syscalls/set_thread_area/set_thread_area01 crashes valgrind:

==5690== Syscall param set_thread_area(u_info) points to unaddressable byte(s)
==5690==    at 0x4129977: syscall (in /usr/lib/libc-2.23.so)
==5690==    by 0x8049A7B: main (set_thread_area01.c:77)
==5690==  Address 0xfffffff7 is not stack'd, malloc'd or (recently) free'd
==5690== 
--5690-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--5690-- si_code=1;  Faulting address: 0xFFFFFFF7;  sp: 0x62a5fe30

valgrind: the 'impossible' happened:
   Killed by fatal signal

host stacktrace:
==5690==    at 0x380B5F3C: sys_set_thread_area (syswrap-x86-linux.c:641)


Reproducible: Always
Comment 1 Mark Wielaard 2016-09-26 21:13:04 UTC
Created attachment 101307 [details]
linux-x86 check get/set_thread_area pointer before use.
Comment 2 Mark Wielaard 2016-10-01 11:56:57 UTC
valgrind svn r15996