This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/18357] New: brk and sbrk are not thread-safe
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 29 Apr 2015 14:55:17 +0000
- Subject: [Bug malloc/18357] New: brk and sbrk are not thread-safe
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18357
Bug ID: 18357
Summary: brk and sbrk are not thread-safe
Product: glibc
Version: 2.21
Status: NEW
Severity: normal
Priority: P2
Component: malloc
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
Target Milestone: ---
Flags: security-
Most architecture implementations maintain a __curbrk variable and do not
synchronize access to it.
brk is kind-of necessarily thread-unsafe by its interface, but sbrk is not
because it uses a relative address. I am not sure if it is worth fixing the
multi-threading issue, or if we just should update the manual.
--
You are receiving this mail because:
You are on the CC list for the bug.