This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/21082] New: loader did not check result when allocating tlsblocks
- From: "ma.jiang at zte dot com.cn" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 25 Jan 2017 09:30:03 +0000
- Subject: [Bug dynamic-link/21082] New: loader did not check result when allocating tlsblocks
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21082
Bug ID: 21082
Summary: loader did not check result when allocating tlsblocks
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: ma.jiang at zte dot com.cn
Target Milestone: ---
Created attachment 9771
--> https://sourceware.org/bugzilla/attachment.cgi?id=9771&action=edit
patch to fix the bug
Hi all,
I found the dynamic linker did not check the return value when allocating
tlsblocks(csu/libc-tls.c and elf/rtld.c). There are some explanations in
comments, but they failed to convince me. Users will only get a segment-fault
when there are no memory for tlsblocks. They will get confused as there are no
helping message printed. Moreover, there many similar checks for memory
allocations. So ,why not do the same for tlsblocks?
I have added a patch to fix the problem(see attachment), it that ok for
trunk?
--
You are receiving this mail because:
You are on the CC list for the bug.