From owner-freebsd-current@FreeBSD.ORG Wed Sep 17 09:24:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA7EA1065685; Wed, 17 Sep 2008 09:24:09 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3C58FC2F; Wed, 17 Sep 2008 09:24:04 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id E4D7F170E4; Wed, 17 Sep 2008 09:24:02 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m8H9O1Si089741; Wed, 17 Sep 2008 09:24:01 GMT (envelope-from phk@critter.freebsd.dk) To: Andrey Chernov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 17 Sep 2008 13:01:01 +0400." <20080917090101.GC57480@nagual.pp.ru> Date: Wed, 17 Sep 2008 09:24:01 +0000 Message-ID: <89740.1221643441@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Daniel Eischen , Max Laier , freebsd-current@freebsd.org Subject: Re: Is fork() hook ever possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2008 09:24:09 -0000 In message <20080917090101.GC57480@nagual.pp.ru>, Andrey Chernov writes: >On Wed, Sep 17, 2008 at 08:04:57AM +0000, Poul-Henning Kamp wrote: >> >The situation is not so simple since the library functions can call >> >ar4random() internally (like mktemp() family already and always does) >> >> I have a really hard time seeing how this could become a performance >> issue, ever. > >The performance issue happens when application tries to call arc4random() >in the loop. That is not what we are talking about, we are talking about the calls in mktemp and similar. >> The solution however, is simple: Just have these hidden library calls >> to arc4random call a wrapper function that does the pid check. > >We can control our own arc4random() internal calls inside our own libs in >such way but can't control 3rd party libs or programs arc4random() calls >(consider ports). We are not obliged to control these calls. If their authors do something stupid, it's not our problem. You are, as usual, trying to vastly overengineer a minor problem that has a simple solution. Just have the FreeBSD library calls, call the wrapper function that does a pid check and be done with it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.