public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/4350] New: Reentrancy problem between strftime() and setenv() Date: Thu, 12 Apr 2007 13:42:00 -0000 [thread overview] Message-ID: <20070412144239.4350.pasky@suse.cz> (raw) Threaded programs may crash randomly if strftime() and setenv() aren't excluded from being called in parallel, since getenv() is called from the inside of strftime(). While getenv()-setenv() thread safety problems are documented, it is not documented that time functions have these problems as well. The proposed patch introduces getenv_r() as a reentrant version of getenv() and uses it from inside of the time functions; maybe you'll choose a different approach (or a different name for the function or so), but something should be done about this. Also, maybe other parts of glibc making use of getenv() might need the same fix. -- Summary: Reentrancy problem between strftime() and setenv() Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: pasky at suse dot cz CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=4350 ------- 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:[~2007-04-12 13:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-12 13:42 pasky at suse dot cz [this message] 2007-04-12 13:43 ` [Bug libc/4350] " pasky at suse dot cz 2007-04-12 13:45 ` pasky at suse dot cz 2007-04-13 17:50 ` jakub at redhat dot com 2007-04-26 17:11 ` pasky at suse dot cz
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=20070412144239.4350.pasky@suse.cz \ --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).