public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/15142] New: Missing locking in _IO_cleanup Date: Wed, 13 Feb 2013 13:12:00 -0000 [thread overview] Message-ID: <bug-15142-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15142 Bug #: 15142 Summary: Missing locking in _IO_cleanup Product: glibc Version: 2.3.4 Status: NEW Severity: normal Priority: P2 Component: stdio AssignedTo: unassigned@sourceware.org ReportedBy: schwab@linux-m68k.org Classification: Unclassified Created attachment 6870 --> http://sourceware.org/bugzilla/attachment.cgi?id=6870 Testcase When _IO_flush_all_lockp is called from _IO_cleanup it doesn't do any locking on _IO_list_all, which races with fopen/fclose from other threads. This can result in heap corruption. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-13 13:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-13 13:12 schwab@linux-m68k.org [this message] 2013-02-14 20:13 ` [Bug stdio/15142] " bugdal at aerifal dot cx 2014-03-25 9:24 ` schwab@linux-m68k.org 2014-06-13 18:49 ` fweimer at redhat dot com 2023-06-04 22:16 ` ppluzhnikov at google dot com 2023-07-03 9:08 ` fweimer at redhat dot com 2024-03-13 10:13 ` dvyukov at google dot com 2024-03-13 10:23 ` fweimer at redhat dot com 2024-03-13 10:28 ` dvyukov at google dot com 2024-03-13 10:43 ` fweimer at redhat 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=bug-15142-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).