From owner-freebsd-testing@FreeBSD.ORG Thu Feb 27 08:18:09 2014 Return-Path: Delivered-To: freebsd-testing@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 256FDD91 for ; Thu, 27 Feb 2014 08:18:09 +0000 (UTC) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id B7DAA1778 for ; Thu, 27 Feb 2014 08:18:08 +0000 (UTC) Received: (qmail 53715 invoked from network); 27 Feb 2014 08:18:01 -0000 Received: from 87.58.146.155 (HELO x2.osted.lan) (87.58.146.155) by relay03.pair.com with SMTP; 27 Feb 2014 08:18:01 -0000 X-pair-Authenticated: 87.58.146.155 Received: from x2.osted.lan (localhost [127.0.0.1]) by x2.osted.lan (8.14.5/8.14.5) with ESMTP id s1R8I03r030166 for ; Thu, 27 Feb 2014 09:18:00 +0100 (CET) (envelope-from pho@x2.osted.lan) Received: (from pho@localhost) by x2.osted.lan (8.14.5/8.14.5/Submit) id s1R8I0Lc030163 for freebsd-testing@freebsd.org; Thu, 27 Feb 2014 09:18:00 +0100 (CET) (envelope-from pho) Date: Thu, 27 Feb 2014 09:17:59 +0100 From: Peter Holm To: freebsd-testing@freebsd.org Subject: 100% repeatability? Message-ID: <20140227081759.GA29517@x2.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 08:18:09 -0000 I looked at creating a test scenario for the following piece of code from src/sys/kern/kern_fork.c: 881 if ((nprocs >= maxproc - 10 && priv_check_cred(td->td_ucred, 882 PRIV_MAXPROC, 0) != 0) || nprocs >= maxproc) { 883 error = EAGAIN; 884 goto fail; 885 } I came up with a test scenario for this: http://people.freebsd.org/~pho/kern_fork_test.c But it is not 100% repeatable, as I would expect many other kernel tests will be. The test case runs as expected, until for example root decides to do a parallel buildworld. Is this a show stopper? -- Peter