From owner-freebsd-arch@FreeBSD.ORG Thu Dec 27 16:12:46 2007 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50FB616A417; Thu, 27 Dec 2007 16:12:46 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (vlk.vlakno.cz [62.168.28.247]) by mx1.freebsd.org (Postfix) with ESMTP id 0BDDA13C45B; Thu, 27 Dec 2007 16:12:46 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id E849F66B003; Thu, 27 Dec 2007 16:55:07 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (vlk.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 566F08Db+cHw; Thu, 27 Dec 2007 16:54:55 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id C8F6D66AFFF; Thu, 27 Dec 2007 16:54:55 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.13.8/8.13.8/Submit) id lBRFstlR023615; Thu, 27 Dec 2007 16:54:55 +0100 (CET) (envelope-from rdivacky) Date: Thu, 27 Dec 2007 16:54:55 +0100 From: Roman Divacky To: John Baldwin Message-ID: <20071227155455.GA23604@freebsd.org> References: <20071218092222.GA9695@freebsd.org> <200712201138.56423.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200712201138.56423.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: arch@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: final decision about *at syscalls X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 16:12:46 -0000 > Considering Robert's paper on security race problems in things like systrace > stemming from when you copy parameters out of userland and into the kernel > multiple times, I think #2 is definitely the better choice. Also, namei() is > already thread aware AFAICT since 'struct componentname' already contains a > 'cnp_thread' member (was 'cnp_proc' in 4.x). two strong voices for #2, I am going that way... thnx