public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/16418] [powerpc] ppc's get_clockfreq is racy and cancel-unsafe Date: Wed, 21 Jan 2015 15:54:00 -0000 [thread overview] Message-ID: <bug-16418-131-zCXtihl41I@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16418-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16418 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, master has been updated via 6b2ba95b6baab6b1789e8823c8a808e09bc98794 (commit) from 191220b3065c659065f8c1e5282ea6410aa47a93 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6b2ba95b6baab6b1789e8823c8a808e09bc98794 commit 6b2ba95b6baab6b1789e8823c8a808e09bc98794 Author: Adhemerval Zanella <azanella@linux.vnet.ibm.com> Date: Mon Nov 24 16:18:26 2014 -0500 BZ #16418: Fix powerpc get_clockfreq raciness This patch fix powerpc __get_clockfreq racy and cancel-safe issues by dropping internal static cache and by using nocancel file operations. The vDSO failure check is also removed, since kernel code does not return an error (it cleans cr0.so bit on function return) and the static code (to read value /proc) now uses non-cancellable calls. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 6 + NEWS | 18 ++-- sysdeps/unix/sysv/linux/powerpc/get_clockfreq.c | 128 +++++++++++------------ 3 files changed, 74 insertions(+), 78 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-01-21 15:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-09 5:52 [Bug ports/16418] New: " aoliva at sourceware dot org 2014-02-07 3:06 ` [Bug libc/16418] [powerpc] " jsm28 at gcc dot gnu.org 2014-06-13 9:09 ` fweimer at redhat dot com 2014-11-24 20:43 ` azanella at linux dot vnet.ibm.com 2015-01-21 15:54 ` cvs-commit at gcc dot gnu.org [this message] 2015-01-21 15:56 ` azanella at linux dot vnet.ibm.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-16418-131-zCXtihl41I@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).