From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24396 invoked by alias); 16 Feb 2012 16:35:19 -0000 Received: (qmail 24108 invoked by uid 22791); 16 Feb 2012 16:35:13 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 16 Feb 2012 16:34:27 +0000 From: "carlos at systemhalted dot org" To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access Date: Thu, 16 Feb 2012 16:35: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-Keywords: glibc_2.15 X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at systemhalted dot org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: carlos at systemhalted dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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 X-SW-Source: 2012-02/txt/msg00145.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=13690 --- Comment #10 from Carlos O'Donell 2012-02-16 16:32:43 UTC --- (In reply to comment #9) > For all bugs like this, I suspect hitting the race condition will require > running the test case for months or years. That's part of why bugs like this > are so frustrating: imagine your mission-critical system crashing just a couple > times a year and the crash not being reproducible. It might be easier to hit > the race with some extreme usage of scheduling priorities to prevent the > unlocking thread from executing for a long time. I agree, but a test case need not be an exact representation of your application under test. The trick I normally use is to preload an auditing library and use the plt_enter and plt_exit stubs to slow down a thread, widening the race window or in some cases making it a 100% reliable reproducer. Such a trick is a perfectly acceptable way to make a test case, but might be hard to use in this situation. -- 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.