From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13490 invoked by alias); 5 Sep 2014 17:42:21 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 13460 invoked by uid 48); 5 Sep 2014 17:42:18 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/17351] No hardware with functional lock elision available Date: Fri, 05 Sep 2014 17:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-09/txt/msg00030.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17351 --- Comment #3 from Carlos O'Donell --- (In reply to Cedric BAIL from comment #2) > Did you choose to force the microcode update on Redhat ? If not how do you > advise user who have random crash and have absolutely no clue where to look > ? Please contact Red Hat support for an answer to this question. No RHEL glibc enables lock elision. > I don't know if you know, but rust has build a work around this bug to > prevent bug from happening on software build with it : > https://github.com/rocallahan/rr/commit/ > d389eb724a9b5f895f813600d9276e00dc063068 . That isn't a workaround for the errata. Rust is disabling elision in glibc for their own reasons, it isn't disabling elision in general. Other applications will continue to check the cpuid RTM bit and use elision. You as a user must make an informed choice to update or not update the microcode for the errata issue. And Fedora glibc will continue to support those users that wish to use RTM on those CPUs. -- You are receiving this mail because: You are on the CC list for the bug.