public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/3317] New: Overriding free which clobbers data and calls pthread_getspecific can get bad value Date: Sat, 07 Oct 2006 01:38:00 -0000 [thread overview] Message-ID: <20061007013816.3317.ian@airs.com> (raw) If I override the libc free() function, and change that function to clobber some bytes of the data, and then call pthread_getspecific from that function, pthread_getspecific can return bad data. This is because __nptl_deallocate_tsd frees data before clearing the pointer to that data. This happens around line 185: /* The first block is allocated as part of the thread descriptor. */ free (level2); THREAD_SETMEM_NC (self, specific, cnt, NULL); The order of those lines should be reversed. I first noticed this bug in linuxthreads, and then discovered that NPTL had the same bug. I will file a separate bug against linuxthreads. I will attach a test case which shows the problem on i686-pc-linux-gnu using Fedora Core 4 with glibc-2.3.6-3. -- Summary: Overriding free which clobbers data and calls pthread_getspecific can get bad value Product: glibc Version: 2.3.6 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: ian at airs dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3317 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-10-07 1:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-07 1:38 ian at airs dot com [this message] 2006-10-07 1:39 ` [Bug nptl/3317] " ian at airs dot com 2006-10-07 20:46 ` drepper at redhat dot com 2006-10-12 5:59 ` ian at airs dot com 2006-10-12 21:18 ` drepper at redhat dot com 2006-10-13 5:26 ` ian at airs dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20061007013816.3317.ian@airs.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).