From owner-cvs-src-old@FreeBSD.ORG Sun Dec 7 02:32:58 2008 Return-Path: Delivered-To: cvs-src-old@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C61821065675 for ; Sun, 7 Dec 2008 02:32:58 +0000 (UTC) (envelope-from peter@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id B42658FC12 for ; Sun, 7 Dec 2008 02:32:58 +0000 (UTC) (envelope-from peter@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id mB72Wwdb060589 for ; Sun, 7 Dec 2008 02:32:58 GMT (envelope-from peter@repoman.freebsd.org) Received: (from svn2cvs@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id mB72WwxV060588 for cvs-src-old@freebsd.org; Sun, 7 Dec 2008 02:32:58 GMT (envelope-from peter@repoman.freebsd.org) Message-Id: <200812070232.mB72WwxV060588@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: svn2cvs set sender to peter@repoman.freebsd.org using -f From: Peter Wemm Date: Sun, 7 Dec 2008 02:32:49 +0000 (UTC) To: cvs-src-old@freebsd.org X-FreeBSD-CVS-Branch: HEAD Subject: cvs commit: src/lib/libthr/thread thr_rtld.c X-BeenThere: cvs-src-old@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: **OBSOLETE** CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 02:32:58 -0000 peter 2008-12-07 02:32:49 UTC FreeBSD src repository Modified files: lib/libthr/thread thr_rtld.c Log: SVN rev 185728 on 2008-12-07 02:32:49Z by peter When libthr and rtld start up, there are a number of magic spells cast in order to get the symbol binding state "just so". This is to allow locking to be activated and not run into recursion problems later. However, one of the magic bits involves an explicit call to _umtx_op() to force symbol resolution. It does a wakeup operation on a fake, uninitialized (ie: random contents) umtx. Since libthr isn't active, this is harmless. Nothing can match the random wakeup. However, valgrind finds this and is not amused. Normally I'd just write a suppression record for it, but the idea of passing random args to syscalls (on purpose) just doesn't feel right. Revision Changes Path 1.10 +1 -1 src/lib/libthr/thread/thr_rtld.c