From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 23 00:10:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A0512C6 for ; Sun, 23 Feb 2014 00:10:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 238281AA3 for ; Sun, 23 Feb 2014 00:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1N0A0g5017000 for ; Sun, 23 Feb 2014 00:10:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1N0A0Db016999; Sun, 23 Feb 2014 00:10:00 GMT (envelope-from gnats) Date: Sun, 23 Feb 2014 00:10:00 GMT Message-Id: <201402230010.s1N0A0Db016999@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Alexander Kabaev Subject: Re: misc/186435: [patch] Allow for an alternative run-time loader X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Alexander Kabaev List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 00:10:01 -0000 The following reply was made to PR misc/186435; it has been noted by GNATS. From: Alexander Kabaev To: bug-followup@FreeBSD.org, yuri@rawbw.com Cc: Subject: Re: misc/186435: [patch] Allow for an alternative run-time loader Date: Sat, 22 Feb 2014 19:06:01 -0500 --Sig_/Tb3vvaIPFtNSK39JaXljUWg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I do not like this patch at all, sorry. While I do appreciate the goal, the way taken here is just wrong - the locking done by rtld internally is just that - internal detail that is not to be paraded publicly in front of an an innocent outside world. Over several last years we have been over several lock implementations and locking semantics have changed subtly couple more times. Would you be willing instead to formulate a functional interface that rtld can expose to provide necessary services to add/remove dynamic objects and that will allow us to keep all of this dirty laundry under the wraps? =20 The patch as is cannot be committed. --=20 Alexander Kabaev --Sig_/Tb3vvaIPFtNSK39JaXljUWg Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iD8DBQFTCTtuQ6z1jMm+XZYRAo4kAKDeEmJUOFOGCBHCW0mIJHGmIoHVGQCdHghZ nfpWQhdtTvw4/Tu4Z+t3Nhw= =pS/v -----END PGP SIGNATURE----- --Sig_/Tb3vvaIPFtNSK39JaXljUWg--